From: Daniel Baluta <daniel.baluta@gmail.com>
To: Maxin John <maxin.john@gmail.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
naveen yadav <yad.naveen@gmail.com>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: kmemleak for MIPS
Date: Tue, 29 Mar 2011 22:54:50 +0300 [thread overview]
Message-ID: <AANLkTimu54k-EEqfN58-hNTTgc54HktEeao+TyaKD30Z@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=gMP6jQuQFovfsOX=7p-SSnwXoVLO_DVEpV63h@mail.gmail.com>
On Tue, Mar 29, 2011 at 10:36 PM, Maxin John <maxin.john@gmail.com> wrote:
> Hi,
>
> I have prepared the combined patch for kmemleak porting to MIPS. After
> applying the patch and enabling the kmemleak in Kernel, I can see one
> kernel memleak reported during booting itself:
> ..
> ..
>
> TCP cubic registered
> NET: Registered protocol family 17
> NET: Registered protocol family 15
> kmemleak: Kernel memory leak detector initialized
> rtc_cmos rtc_cmos: setting system clock to 2011-03-29 18:20:41 UTC (1301422841)
> kmemleak: Automatic memory scanning thread started
> EXT3-fs: barriers not enabled
> kjournald starting. Commit interval 5 seconds
> EXT3-fs (hda1): mounted filesystem with ordered data mode
> VFS: Mounted root (ext3 filesystem) readonly on device 3:1.
> Freeing prom memory: 956k freed
> Freeing unused kernel memory: 244k freed
> modprobe: FATAL: Could not load
> /lib/modules/2.6.38-08826-g1788c20-dirty/modules.dep: No such file or
> directory
>
> INIT: version 2.86 booting
> Starting the hotplug events dispatcher: udevdudevd (863):
> /proc/863/oom_adj is deprecated, please use /proc/863/oom_score_adj
> instead.
> .
> Synthesizing the initial hotplug events...done.
> Waiting for /dev to be fully populated...kmemleak: 1 new suspected
> memory leaks (see /sys/kernel/debug/kmemleak)
> ....
> ....
>
> debian-mips:~#
> debian-mips:~# mount -t debugfs nodev /sys/kernel/debug/
> debian-mips:~# cat /sys/kernel/debug/kmemleak
> unreferenced object 0x8f90d000 (size 4096):
> comm "swapper", pid 1, jiffies 4294937330 (age 815.000s)
> 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:
> [<80529644>] alloc_large_system_hash+0x2f8/0x410
> [<805383b4>] udp_table_init+0x4c/0x158
> [<805384dc>] udp_init+0x1c/0x94
> [<8053889c>] inet_init+0x184/0x2a0
> [<80100584>] do_one_initcall+0x174/0x1e0
> [<8051f348>] kernel_init+0xe4/0x174
> [<80103d4c>] kernel_thread_helper+0x10/0x18
>
>
> The standard kmemleak test case is behaving as expected. Based on
> this, I think, we can say that the kmemleak support for MIPS is
> working.
>
> Please let me know your comments.
This looks good to me.
thanks,
Daniel.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-03-29 19:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 13:54 naveen yadav
2011-03-24 9:27 ` Daniel Baluta
2011-03-24 9:55 ` Catalin Marinas
2011-03-28 21:15 ` Maxin John
2011-03-29 10:40 ` Catalin Marinas
2011-03-29 11:38 ` Maxin John
2011-03-29 11:50 ` Catalin Marinas
2011-03-29 12:27 ` Maxin John
2011-03-29 19:36 ` Maxin John
2011-03-29 19:54 ` Daniel Baluta [this message]
2011-03-30 9:15 ` Catalin Marinas
2011-03-30 9:54 ` Daniel Baluta
2011-03-30 9:58 ` Catalin Marinas
2011-03-30 11:03 ` Maxin John
2011-03-30 11:24 ` Daniel Baluta
2011-03-30 11:38 ` Catalin Marinas
2011-03-30 12:17 ` Maxin John
2011-03-30 12:27 ` Eric Dumazet
2011-03-30 12:40 ` Maxin John
2011-03-30 12:52 ` Daniel Baluta
2011-03-30 13:17 ` Maxin John
2011-03-30 13:27 ` Eric Dumazet
2011-03-30 14:07 ` Maxin John
2011-03-30 14:07 ` Catalin Marinas
2011-03-30 12:22 ` Eric Dumazet
2011-03-30 10:08 ` Maxin John
2011-03-30 14:28 ` Ralf Baechle
2011-03-30 14:21 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2009-11-02 17:07 Kmemleak for mips Luis R. Rodriguez
2009-11-03 9:23 ` Catalin Marinas
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=AANLkTimu54k-EEqfN58-hNTTgc54HktEeao+TyaKD30Z@mail.gmail.com \
--to=daniel.baluta@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mm@kvack.org \
--cc=maxin.john@gmail.com \
--cc=yad.naveen@gmail.com \
/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