From: Catalin Marinas <catalin.marinas@arm•com>
To: Matthias Kaehlcke <matthias@kaehlcke•net>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for April 22: kmemleak: unreferenced object
Date: Thu, 23 Apr 2009 12:01:29 +0100 [thread overview]
Message-ID: <1240484489.20564.32.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <20090422124932.GA26289@traven>
On Wed, 2009-04-22 at 14:49 +0200, Matthias Kaehlcke wrote:
> shortly after booting next-20090422 on an ep9301, kmemleak complains
> about an unreferenced object:
>
> kmemleak: unreferenced object 0xc5408610 (size 5):
> comm "swapper", pid 0, jiffies 4294937323
> backtrace:
> [<c00267e0>] save_stack_trace+0x24/0x28
> [<c00a3db4>] kmemleak_alloc+0x144/0x2cc
> [<c00a211c>] __kmalloc_node+0x1bc/0x1d4
> [<c008d730>] kstrdup+0x3c/0x54
> [<c00bedec>] alloc_vfsmnt+0x9c/0x148
> [<c00a7c10>] vfs_kern_mount+0x34/0xa8
> [<c00a7ca4>] kern_mount_data+0x20/0x24
> [<c0013428>] bdev_cache_init+0x54/0xa0
> [<c0012c74>] vfs_caches_init+0x104/0x140
> [<c0008980>] start_kernel+0x244/0x2b8
> [<00008034>] 0x8034
> [<ffffffff>] 0xffffffff
That's a known leak happening in bdev_cache_init() - the bd_mnt pointer
is never freed (and people argued that we shouldn't be bothered with
freeing it). I marked it with kmemleak_ignore() but forgot about the
block allocated by kstrdup() in alloc_vfsmnt() and referenced from the
vfsmount structure.
I'll change kmemleak_ignore() to kmemleak_not_leak() so that the
vfsmount structure is scanned for other referenced objects.
Thanks.
--
Catalin
next prev parent reply other threads:[~2009-04-23 11:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 5:42 linux-next: Tree for April 22 Stephen Rothwell
2009-04-22 8:41 ` linux-next: Tree for April 22 [BUG] ep93xx_keypad_open: undefined reference to `clk_set_rate' Matthias Kaehlcke
2009-04-22 16:55 ` linux-next: Tree for April 22 [BUG] ep93xx_keypad_open:undefined " H Hartley Sweeten
2009-04-22 10:38 ` April 22 Next : net/rfkill randconfig failure Sachin Sant
2009-04-23 9:54 ` Alexander Beregalov
2009-04-23 10:33 ` Ken Lewis
2009-04-22 12:49 ` linux-next: Tree for April 22: kmemleak: unreferenced object Matthias Kaehlcke
2009-04-23 11:01 ` Catalin Marinas [this message]
2009-04-22 16:53 ` linux-next: Tree for April 22 (rndis_wlan) Randy Dunlap
[not found] ` <49EF4B73.2050702-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-04-22 17:28 ` John W. Linville
2009-04-22 19:06 ` Randy Dunlap
[not found] ` <20090422172804.GE3288-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2009-04-22 21:08 ` Jussi Kivilinna
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=1240484489.20564.32.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=matthias@kaehlcke$(echo .)net \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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