Skip to contentSkip to conversation

3.x memleaks

DISCUSSION Sid Boyce 2 participants 3 messages Sep 6, 2011 – Sep 8, 2011

lore
Share & tools
lore

Sid Boyce

author
#0 lore raw

Since 3.0 I have been seeing memleaks, right up to 3.1.0-rc5. This is typical. AMD x86_64, X2, X4's and openSUSE 12.1 Milestones.
unreferenced object 0xffff88022f007000 (size 512):
comm "swapper", pid 1, jiffies 4294667649 (age 17727.056s)
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:
    [<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
    [<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
    [<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
    [<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
    [<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
    [<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
    [<ffffffff81c36cca>] kernel_init+0xb8/0x159
    [<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
    [<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88022f007600 (size 512):
  comm "swapper", pid 1, jiffies 4294667649 (age 17727.056s)
  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:
    [<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
    [<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
    [<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
    [<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
    [<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
    [<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
    [<ffffffff81c36cca>] kernel_init+0xb8/0x159
    [<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
    [<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88022f007800 (size 512):
  comm "swapper", pid 1, jiffies 4294667649 (age 17727.056s)
  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:
    [<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
    [<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
    [<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
    [<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
    [<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
    [<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
    [<ffffffff81c36cca>] kernel_init+0xb8/0x159
    [<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
    [<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88022f007a00 (size 512):
  comm "swapper", pid 1, jiffies 4294667649 (age 17727.056s)
  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:
    [<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
    [<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
    [<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
    [<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
    [<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
    [<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
    [<ffffffff81c36cca>] kernel_init+0xb8/0x159
    [<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
    [<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88022f007c00 (size 512):
  comm "swapper", pid 1, jiffies 4294667649 (age 17727.056s)
  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:
    [<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
    [<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
    [<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
    [<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
    [<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
    [<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
    [<ffffffff81c36cca>] kernel_init+0xb8/0x159
    [<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
    [<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88022f007e00 (size 512):
  comm "swapper", pid 1, jiffies 4294667649 (age 18070.657s)
  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:
    [<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
    [<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
    [<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
    [<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
    [<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
    [<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
    [<ffffffff81c36cca>] kernel_init+0xb8/0x159
    [<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
    [<ffffffffffffffff>] 0xffffffffffffffff
****** the rest truncated *************

Regards
Sid.

Signature · 4 lines
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
#1 lore raw
Quoted 17 lines · Sid Boyce

Since 3.0 I have been seeing memleaks, right up to 3.1.0-rc5. This is typical.
AMD x86_64, X2, X4's and openSUSE 12.1 Milestones. unreferenced object 0xffff88022f007000 (size 512):
 comm "swapper", pid 1, jiffies 4294667649 (age 17727.056s) 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:

   [<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
   [<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
   [<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
   [<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
   [<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
   [<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
   [<ffffffff81c36cca>] kernel_init+0xb8/0x159
   [<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
Quoted 1 line

   [<ffffffffffffffff>] 0xffffffffffffffff

Hello,

This should be fixed by: https://lkml.org/lkml/2011/8/29/218

Thanks!

author
#2 lore raw
Quoted 19 lines · Américo Wang
Quoted 9 lines · Sid Boyce

Since 3.0 I have been seeing memleaks, right up to 3.1.0-rc5. This is typical.
AMD x86_64, X2, X4's and openSUSE 12.1 Milestones. unreferenced object 0xffff88022f007000 (size 512):
 comm "swapper", pid 1, jiffies 4294667649 (age 17727.056s)  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:

Quoted 9 lines
   [<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
   [<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
   [<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
   [<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
   [<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
   [<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
   [<ffffffff81c36cca>] kernel_init+0xb8/0x159
   [<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
   [<ffffffffffffffff>] 0xffffffffffffffff
Quoted 6 lines

Hello,

This should be fixed by: https://lkml.org/lkml/2011/8/29/218

Thanks!

I applied the patch to 3.1-rc5 and it's still the same. Regards
Sid.

Signature · 4 lines
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks