From: Jeff Dike <jdike@addtoit.com>
To: Thorsten Knabe <linux@thorsten-knabe.de>
Cc: Chris Wright <chrisw@sous-sol.org>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] Linux 2.6.25.4 task_struct leak
Date: Wed, 4 Jun 2008 20:49:25 -0400 [thread overview]
Message-ID: <20080605004925.GA15461@c2.user-mode-linux.org> (raw)
In-Reply-To: <484719C7.2020502@thorsten-knabe.de>
On Thu, Jun 05, 2008 at 12:40:07AM +0200, Thorsten Knabe wrote:
> I can start other 32-bit applications, for example compile an UML
> kernel, within the chroot without leaking task_structs, but as soon as I
> start an UML instance, I see leaked task_structs. Starting and
> immediately shutting down an UML instacne leaks approximately 2000
> task_structs. The number of leaked task_structs on the host seems to be
> equal to the number of processes that have been created (and destroyed)
> within the UML instances.
I misunderstood - I thought you were seeing a task_struct leak within
UML rather than a leak on the host elicited by UML.
> As far as I understand the UML code in the kernel, an UML kernel uses
> some unusual clone() flags when creating new processes, which are seldom
> used by other applications and could be related to the bug.
Yes, it does. I don't see the flags causing a leak, though. What
might be more likely (although I really have no idea) is ptrace.
Possibly a reference is held when it should have been dropped. This
might also show up with strace or gdb.
Jeff
--
Work email - jdike at linux dot intel dot com
next prev parent reply other threads:[~2008-06-05 0:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 15:05 [BUG] Linux 2.6.25.4 task_struct leak Thorsten Knabe
2008-06-01 21:31 ` Chris Wright
2008-06-02 1:05 ` Jeff Dike
2008-06-04 22:40 ` Thorsten Knabe
2008-06-05 0:49 ` Jeff Dike [this message]
2008-06-05 1:06 ` Chris Wright
2008-06-08 11:39 ` Thorsten Knabe
2008-06-08 14:34 ` WANG Cong
2008-06-12 18:58 ` Roland McGrath
2008-06-12 19:01 ` [PATCH stable-2.6.25] x86_64 ptrace: fix sys32_ptrace " Roland McGrath
2008-06-30 6:44 ` Ingo Molnar
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=20080605004925.GA15461@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@thorsten-knabe.de \
/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