From: Andrew Morton <akpm@linux-foundation.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>,
Serge Hallyn <serue@us.ibm.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Sukadev Bhattiprolu <sukadev@us.ibm.com>
Subject: Re: [2.6.31 and later] "struct pid" leak.
Date: Wed, 31 Mar 2010 15:17:19 -0700 [thread overview]
Message-ID: <20100331151719.8a92b302.akpm@linux-foundation.org> (raw)
In-Reply-To: <tnxbpe5ygfy.fsf@e102109-lin.cambridge.arm.com>
On Tue, 30 Mar 2010 16:31:13 +0100
Catalin Marinas <catalin.marinas@arm.com> wrote:
> Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> wrote:
> > I got below report with 2.6.33.1 .
> >
> > unreferenced object 0xde144600 (size 64):
> > comm "init", pid 1, jiffies 4294678101 (age 291.508s)
> > hex dump (first 32 bytes):
> > 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> > 00 00 00 00 04 76 ae de d1 76 43 c0 d6 08 00 00 .....v...vC.....
> > backtrace:
> > [<c0481704>] create_object+0x121/0x1ef
> > [<c05f546b>] kmemleak_alloc+0x25/0x42
> > [<c047e326>] kmemleak_alloc_recursive+0x1c/0x22
> > [<c047e36e>] kmem_cache_alloc+0x42/0x68
> > [<c0437701>] alloc_pid+0x19/0x288
> > [<c0428acc>] copy_process+0x95a/0xdac
> > [<c04290d8>] do_fork+0x129/0x261
> > [<c0407de5>] sys_clone+0x1f/0x24
> > [<c040292d>] ptregs_clone+0x15/0x28
> > [<ffffffff>] 0xffffffff
> > unreferenced object 0xdfa96a40 (size 64):
> > comm "login", pid 2259, jiffies 4294719437 (age 250.179s)
> > hex dump (first 32 bytes):
> > 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> > 00 00 00 00 60 39 ae de d1 76 43 c0 bb 09 00 00 ....`9...vC.....
> > backtrace:
> > [<c0481704>] create_object+0x121/0x1ef
> > [<c05f546b>] kmemleak_alloc+0x25/0x42
> > [<c047e326>] kmemleak_alloc_recursive+0x1c/0x22
> > [<c047e36e>] kmem_cache_alloc+0x42/0x68
> > [<c0437701>] alloc_pid+0x19/0x288
> > [<c0428acc>] copy_process+0x95a/0xdac
> > [<c04290d8>] do_fork+0x129/0x261
> > [<c0407de5>] sys_clone+0x1f/0x24
> > [<c040292d>] ptregs_clone+0x15/0x28
> > [<ffffffff>] 0xffffffff
>
> I reported similar leaks last year -
> http://lkml.org/lkml/2009/7/8/422. There is some analysis in the thread
> above of the reference counting but I couldn't figure out where it goes
> wrong. It looks to me like there isn't any reference to a struct pid
> block but its reference count is 2.
>
> There is a bugzilla entry as well -
> https://bugzilla.kernel.org/show_bug.cgi?id=13868
>
Let's bug some people by cc'ing them ;)
next prev parent reply other threads:[~2010-03-31 22:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 12:21 [2.6.31 and later] "struct pid" leak Tetsuo Handa
2010-03-30 15:31 ` Catalin Marinas
2010-03-31 22:17 ` Andrew Morton [this message]
2010-04-01 16:52 ` Oleg Nesterov
2010-04-01 17:21 ` Serge E. Hallyn
2010-04-01 17:33 ` Serge E. Hallyn
2010-04-02 15:29 ` Oleg Nesterov
2010-04-02 16:04 ` [PATCH 0/1] tty: release_one_tty() forgets to put pids Oleg Nesterov
2010-04-02 16:05 ` [PATCH 1/1] " Oleg Nesterov
2010-04-02 16:19 ` Oleg Nesterov
2010-04-02 17:46 ` Linus Torvalds
2010-04-02 18:22 ` Eric W. Biederman
2010-04-02 18:48 ` Oleg Nesterov
2010-04-02 18:43 ` Oleg Nesterov
2010-04-02 20:09 ` Alan Cox
2010-04-03 2:40 ` [PATCH 0/1] " Tetsuo Handa
2010-04-03 3:08 ` Linus Torvalds
2010-04-03 5:15 ` [stable] " Greg KH
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=20100331151719.8a92b302.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=serue@us.ibm.com \
--cc=sukadev@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.