[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=RXoEOVmTPiL=dfO97aOVKWOJWE7hoQduPPsCZ@mail.gmail.com>
Date: Wed, 30 Mar 2011 14:17:03 +0100
From: Maxin John <maxin.john@...il.com>
To: Daniel Baluta <daniel.baluta@...il.com>
Cc: Catalin Marinas <catalin.marinas@....com>,
naveen yadav <yad.naveen@...il.com>, linux-mips@...ux-mips.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Eric Dumazet <eric.dumazet@...il.com>
Subject: Re: kmemleak for MIPS
Hi,
I have compiled the kernel with below given modification in .config
CONFIG_CMDLINE="uhash_entries=256"
After booting with the new kernel, the "kmemleak" no longer complains
about the "udp_table_init".
However it do report another possible leak :)
debian-mips:~# cat /sys/kernel/debug/kmemleak
unreferenced object 0x8f085000 (size 4096):
comm "swapper", pid 1, jiffies 4294937670 (age 1043.280s)
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:
[<801ac7a8>] __kmalloc+0x130/0x180
[<80532500>] flow_cache_cpu_prepare+0x50/0xa8
[<8052378c>] flow_cache_init_global+0x90/0x138
[<80100584>] do_one_initcall+0x174/0x1e0
[<8050c348>] kernel_init+0xe4/0x174
[<80103d4c>] kernel_thread_helper+0x10/0x18
debian-mips:~#
> So, I guess everything is fine regarding udp_init_table. We can move on,
> integrating MIPS support for kmemleak :).
>
I completely agree with Daniel. Shall we move on and integrate the
kmemleak support for MIPS ?
Cheers,
Maxin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists