From: Sid Boyce <sboyce@blueyonder.co.uk>
To: LKML Mailing List <linux-kernel@vger.kernel.org>
Subject: 3.x memleaks
Date: Tue, 06 Sep 2011 16:50:38 +0100 [thread overview]
Message-ID: <4E66414E.8060100@blueyonder.co.uk> (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.
--
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
next reply other threads:[~2011-09-06 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 15:50 Sid Boyce [this message]
2011-09-07 10:58 ` 3.x memleaks Américo Wang
2011-09-07 23:37 ` Sid Boyce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E66414E.8060100@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox