Bug 24832 - kmemleak detected leaks
kmemleak detected leaks
Status: RESOLVED NOTABUG
Product: DRI
Classification: Unclassified
Component: DRM/other
unspecified
Other All
: medium normal
Assigned To: Default DRI bug account
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-31 14:07 UTC by Marc Dietrich
Modified: 2009-11-23 02:50 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Dietrich 2009-10-31 14:07:28 UTC
current kernel compiled with kmemleak shows the following (possible) leaks. These may be false positives, but I don't know how to work around them. Hardware is rs690 with kms enabled. 

unreferenced object 0xffff880034c32db0 (size 128):                                   
  comm "work_for_cpu", pid 935, jiffies 4294894952                                   
  hex dump (first 32 bytes):                                                         
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................                
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................                
  backtrace:                                                                         
    [<ffffffff8142d695>] kmemleak_alloc+0x25/0x50                                    
    [<ffffffff810fe0e3>] kmem_cache_alloc+0x163/0x280                                
    [<ffffffffa00e5b80>] ttm_mem_global_init+0x180/0x360 [ttm]                       
    [<ffffffffa014cbdd>] radeon_ttm_mem_global_init+0xd/0x10 [radeon]                
    [<ffffffffa00eb3e8>] ttm_global_item_ref+0x68/0xc0 [ttm]                         
    [<ffffffffa014cc3c>] radeon_ttm_init+0x5c/0x370 [radeon]                         
    [<ffffffffa014d6de>] radeon_object_init+0x7e/0x90 [radeon]                       
    [<ffffffffa016ca6c>] rs690_init+0xcc/0x220 [radeon]                              
    [<ffffffffa013fa7c>] radeon_device_init+0x23c/0x2d0 [radeon]                     
    [<ffffffffa01405b2>] radeon_driver_load_kms+0x92/0x160 [radeon]                  
    [<ffffffffa00105a5>] drm_get_dev+0x325/0x530 [drm]                               
    [<ffffffffa01853de>] radeon_pci_probe+0x10/0x264 [radeon]                        
    [<ffffffff81233542>] local_pci_probe+0x12/0x20                                   
    [<ffffffff81069b53>] do_work_for_cpu+0x13/0x30                                   
    [<ffffffff8106da9e>] kthread+0x8e/0xa0                                           
    [<ffffffff8100ceaa>] child_rip+0xa/0x20                                          
unreferenced object 0xffff88001c78ada8 (size 544):                                   
  comm "glxinfo", pid 4613, jiffies 4294954549                                       
  hex dump (first 32 bytes):                                                         
    02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................                
    78 5b 18 24 00 88 ff ff 00 00 00 00 00 00 00 00  x[.$............                
  backtrace:                                                                         
    [<ffffffff8142d695>] kmemleak_alloc+0x25/0x50                                    
    [<ffffffff810fe0e3>] kmem_cache_alloc+0x163/0x280                                
    [<ffffffff8121b28f>] idr_pre_get+0x5f/0x90                                       
    [<ffffffffa000cfed>] drm_gem_handle_create+0x2d/0xb0 [drm]                       
    [<ffffffffa000d119>] drm_gem_open_ioctl+0xa9/0xf0 [drm]                          
    [<ffffffffa000b4ce>] drm_ioctl+0x16e/0x380 [drm]                                 
    [<ffffffff81116b6c>] vfs_ioctl+0x7c/0xa0                                         
    [<ffffffff81116ca2>] do_vfs_ioctl+0x82/0x590                                     
    [<ffffffff81117229>] sys_ioctl+0x79/0x90                                         
    [<ffffffff8100be42>] system_call_fastpath+0x16/0x1b                              
    [<ffffffffffffffff>] 0xffffffffffffffff
Comment 1 Jerome Glisse 2009-11-23 02:50:21 UTC
These are false positive.