Skip to contentSkip to conversation

2.6.33.2 kmalloc-8 slab leaks ~512 objects per second

DISCUSSION Tvrtko Ursulin 4 participants 9 messages May 12, 2010 – May 26, 2010

lore
Share & tools
lore
#0 lore raw

Hi all,

As the subject says, is this a know issue? I have been tracking the growth at one second intervals and it looks like this:

512 (67716608) Slab:             606744 kB
512 (67717120) Slab:             606752 kB
512 (67717632) Slab:             606756 kB

0 (67718144) Slab: 606756 kB
512 (67718144) Slab: 606760 kB
1024 (67718656) Slab: 606768 kB
512 (67719680) Slab: 606772 kB
512 (67720192) Slab: 606776 kB
0 (67720704) Slab: 606776 kB
512 (67720704) Slab: 606780 kB

First fiels is the diff in numobj, in parentheses is actual numobj and last is the total slab size from /proc/meminfo.

kmalloc-8 68044800 68044800 8 512 1 : tunables 0 0 0
: slabdata 132900 132900 0

dm-io slab also seems large, don't know... :
dm_io 75924 147288 40 102 1 : tunables 0 0 0 :
slabdata 1444 1444 0

Some other info about the system/kernel is attached.

Tvrtko

Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom. Company Reg No 2096520. VAT Reg No GB 348 3873 20.

Module                  Size  Used by
bridge                 49385  0      
stp                     1903  1 bridge
llc                     4749  2 bridge,stp
tun                    12712  4           
nls_utf8                1325  1           
cifs                  249220  2           
power_meter             8721  0           
dell_rbu                5994  0           
nfsd                  103640  7           
exportfs                3808  1 nfsd      
snd_pcm_oss            35939  0           
snd_mixer_oss          14873  1 snd_pcm_oss
snd_seq                51077  0            
snd_seq_device          5913  1 snd_seq    
edd                     8495  0            
nfs                   162373  3            
lockd                  70096  2 nfsd,nfs   
nfs_acl                 2517  2 nfsd,nfs   
sunrpc                206266  27 nfsd,nfs,lockd,nfs_acl
radeon                704591  2                        
ttm                    52379  1 radeon                 
drm_kms_helper         27568  1 radeon                 
drm                   178090  5 radeon,ttm,drm_kms_helper
i2c_algo_bit            5267  1 radeon                   
af_packet              18575  0                          
cpufreq_conservative    10990  0                         
cpufreq_userspace       2240  0                          
cpufreq_powersave       1002  0                          
acpi_cpufreq            6447  0                          
fuse                   61697  1                          
loop                   15435  0                          
snd_hda_codec_realtek   281691  1                        
snd_hda_intel          23948  2                          
snd_hda_codec          70603  2 snd_hda_codec_realtek,snd_hda_intel
dcdbas                  6609  0                                    
snd_hwdep               6250  1 snd_hda_codec                      
snd_pcm                71241  3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
iTCO_wdt                9926  0                                        
snd_timer              19944  2 snd_seq,snd_pcm                        
kvm_intel              42483  3                                        
tg3                   120566  0                                        
iTCO_vendor_support     2563  1 iTCO_wdt                               
broadcom                6767  0
snd                    60878  14 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
kvm                   179805  1 kvm_intel
button                  5413  0
snd_page_alloc          7637  2 snd_hda_intel,snd_pcm
sr_mod                 12762  0
libphy                 20434  2 tg3,broadcom
intel_agp              27929  0
pcspkr                  1870  0
sg                     25183  0
cdrom                  36645  1 sr_mod
ext4                  244065  9
jbd2                   58645  1 ext4
crc16                   1471  1 ext4
linear                  4294  0
raid456                50446  0
async_raid6_recov       5589  1 raid456
async_pq                3529  2 raid456,async_raid6_recov
raid6_pq               79292  2 async_raid6_recov,async_pq
async_xor               2658  3 raid456,async_raid6_recov,async_pq
xor                     4672  1 async_xor
async_memcpy            1490  2 raid456,async_raid6_recov
async_tx                2137  5 raid456,async_raid6_recov,async_pq,async_xor,async_memcpy
raid1                  21608  0
raid0                   6118  1
dm_snapshot            28785  0
dm_mod                 64837  25 dm_snapshot
fan                     3519  0
processor              31361  1 acpi_cpufreq
thermal                13003  0
thermal_sys            15131  3 fan,processor,thermal
#1 lore raw

Hi Tvrtko,

Quoted 17 lines · Tvrtko Ursulin

As the subject says, is this a know issue? I have been tracking the growth at one second intervals and it looks like this:

512 (67716608) Slab:             606744 kB 512 (67717120) Slab:             606752 kB 512 (67717632) Slab:             606756 kB 0 (67718144) Slab:             606756 kB 512 (67718144) Slab:             606760 kB 1024 (67718656) Slab:             606768 kB 512 (67719680) Slab:             606772 kB 512 (67720192) Slab:             606776 kB 0 (67720704) Slab:             606776 kB 512 (67720704) Slab:             606780 kB

First fiels is the diff in numobj, in parentheses is actual numobj and last is the total slab size from /proc/meminfo.

Quoted 8 lines

kmalloc-8         68044800 68044800      8  512    1 : tunables    0    0    0 : slabdata 132900 132900      0

dm-io slab also seems large, don't know... :
dm_io              75924 147288     40  102    1 : tunables    0    0    0 :
slabdata   1444   1444      0

Some other info about the system/kernel is attached.

[snip]

You might want to try out the built-in kernel memory leak detector. See Documentation/kmemleak.txt for details how to enable it and use it.

Pekka

#2 lore raw
Quoted 5 lines · On Wednesday 12 May 2010 14:00:51 Pekka Enberg wrote:

[snip]

You might want to try out the built-in kernel memory leak detector. See Documentation/kmemleak.txt for details how to enable it and use it.

Thanks for the suggestion, I will have to try it out once but not this time :) because 2.6.34-rc7 seems to be fine, or in other words not leaking.

Tvrtko

Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom. Company Reg No 2096520. VAT Reg No GB 348 3873 20.

#3 lore raw
Quoted 9 lines · Tvrtko Ursulin
Quoted 5 lines · On Wednesday 12 May 2010 14:00:51 Pekka Enberg wrote:

[snip]

You might want to try out the built-in kernel memory leak detector. See Documentation/kmemleak.txt for details how to enable it and use it.

Thanks for the suggestion, I will have to try it out once but not this time :) because 2.6.34-rc7 seems to be fine, or in other words not leaking.

You could just enable CONFIG_DEBUG_KMEMLEAK on 2.6.33, mount the debugfs and do a 'cat /sys/kernel/debug/kmemleak' after a half-hour or so.

Signature · 1 line
Catalin
#4 lore raw
Quoted 8 lines · On Thursday 13 May 2010 13:29:49 Catalin Marinas wrote:
Quoted 7 lines · Tvrtko Ursulin
Quoted 5 lines · On Wednesday 12 May 2010 14:00:51 Pekka Enberg wrote:

[snip]

You might want to try out the built-in kernel memory leak detector. See Documentation/kmemleak.txt for details how to enable it and use it.

Quoted 6 lines
Quoted 3 lines

Thanks for the suggestion, I will have to try it out once but not this time :) because 2.6.34-rc7 seems to be fine, or in other words not leaking.

You could just enable CONFIG_DEBUG_KMEMLEAK on 2.6.33, mount the debugfs and do a 'cat /sys/kernel/debug/kmemleak' after a half-hour or so.

I could do it if radeon/drm guys would be interested in those results? (Given how 2.6.34-rc7 is not leaking.)

Tvrtko

Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom. Company Reg No 2096520. VAT Reg No GB 348 3873 20.

#5 lore raw
Quoted 6 lines · Tvrtko Ursulin
Quoted 2 lines

You could just enable CONFIG_DEBUG_KMEMLEAK on 2.6.33, mount the debugfs and do a 'cat /sys/kernel/debug/kmemleak' after a half-hour or so.

I could do it if radeon/drm guys would be interested in those results? (Given how 2.6.34-rc7 is not leaking.)

Did you get a chance to find out if kmemleak was able to identify the source of this problem?

------------------------------------------------------------------------------

--

#6 lore raw
In reply to Tvrtko Ursulin
Quoted 6 lines · Tvrtko Ursulin
Quoted 2 lines

You could just enable CONFIG_DEBUG_KMEMLEAK on 2.6.33, mount the debugfs and do a 'cat /sys/kernel/debug/kmemleak' after a half-hour or so.

I could do it if radeon/drm guys would be interested in those results? (Given how 2.6.34-rc7 is not leaking.)

Did you get a chance to find out if kmemleak was able to identify the source of this problem?

#7 lore raw
Quoted 10 lines · On Wednesday 26 May 2010 10:21:36 David Rientjes wrote:
Quoted 6 lines · Tvrtko Ursulin
Quoted 3 lines

You could just enable CONFIG_DEBUG_KMEMLEAK on 2.6.33, mount the debugfs and do a 'cat /sys/kernel/debug/kmemleak' after a half-hour or so.

I could do it if radeon/drm guys would be interested in those results? (Given how 2.6.34-rc7 is not leaking.)

Did you get a chance to find out if kmemleak was able to identify the source of this problem?

Well no, I asked DRM/radeon guys to explicitly say whether it would be useful, otherwise it is unfortunately sufficiently low on my priority list that it will probably never happen.

Tvrtko

Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom. Company Reg No 2096520. VAT Reg No GB 348 3873 20.

------------------------------------------------------------------------------

--

#8 lore raw
In reply to David Rientjes
Quoted 10 lines · On Wednesday 26 May 2010 10:21:36 David Rientjes wrote:
Quoted 6 lines · Tvrtko Ursulin
Quoted 3 lines

You could just enable CONFIG_DEBUG_KMEMLEAK on 2.6.33, mount the debugfs and do a 'cat /sys/kernel/debug/kmemleak' after a half-hour or so.

I could do it if radeon/drm guys would be interested in those results? (Given how 2.6.34-rc7 is not leaking.)

Did you get a chance to find out if kmemleak was able to identify the source of this problem?

Well no, I asked DRM/radeon guys to explicitly say whether it would be useful, otherwise it is unfortunately sufficiently low on my priority list that it will probably never happen.

Tvrtko

Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom. Company Reg No 2096520. VAT Reg No GB 348 3873 20.