From: WANG Cong <xiyou.wangcong@gmail.com>
To: Thorsten Knabe <linux@thorsten-knabe.de>
Cc: Jeff Dike <jdike@addtoit.com>, Chris Wright <chrisw@sous-sol.org>,
linux-kernel@vger.kernel.org, Roland McGrath <roland@redhat.com>
Subject: Re: [BUG] Linux 2.6.25.4 task_struct leak
Date: Sun, 8 Jun 2008 22:34:34 +0800 [thread overview]
Message-ID: <20080608143434.GF2487@hacking> (raw)
In-Reply-To: <484BC4DF.5000605@thorsten-knabe.de>
On Sun, Jun 08, 2008 at 01:39:11PM +0200, Thorsten Knabe wrote:
>
>Hello Jeff.
>
>Your assumption about ptrace causing the task_struct leak seems to be
>right. I bisected the problem down to a few commits using the repository
>at git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git.
>
>Commit b7b71725fb9584454bfe5f231223bd63421798fb is the last known commit
>that does not leak task_structs, whereas commit
>a97f52e67890fda6b373c1c1895ff1c1c69b36c8 is leaking task_structs.
>Revisions in between do not even compile.
>Also I had to apply the changes from commit
>f9cb02b0be4de3c51edfdd701754e13d9a2d20d6 to most of the kernels I have
>tested, otherwise the UML process would crash on startup.
Add Cc to Roland McGrath <roland@redhat.com>.
--
Hi, I'm a .signature virus, please copy/paste me to help me spread
all over the world.
next prev parent reply other threads:[~2008-06-08 14:38 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
2008-06-05 1:06 ` Chris Wright
2008-06-08 11:39 ` Thorsten Knabe
2008-06-08 14:34 ` WANG Cong [this message]
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=20080608143434.GF2487@hacking \
--to=xiyou.wangcong@gmail.com \
--cc=chrisw@sous-sol.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@thorsten-knabe.de \
--cc=roland@redhat.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.