Re: 3.x memleaks

[AmÃrico Wang]

On Tue, Sep 6, 2011 at 11:50 PM, Sid Boyce <sboyce@xxxxxxxxxxxxxxxx> wrote:
> 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

Hello,

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

Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/