From: Jeff Dike <jdike@addtoit.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Thorsten Knabe <linux@thorsten-knabe.de>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] Linux 2.6.25.4 task_struct leak
Date: Sun, 1 Jun 2008 21:05:46 -0400 [thread overview]
Message-ID: <20080602010546.GA8578@c2.user-mode-linux.org> (raw)
In-Reply-To: <20080601213134.GJ4018@sequoia.sous-sol.org>
On Sun, Jun 01, 2008 at 02:31:39PM -0700, Chris Wright wrote:
> * Thorsten Knabe (linux@thorsten-knabe.de) wrote:
> > [5.] Most recent kernel version which did not have the bug:
> > 2.6.23.17 does not leak task_structs.
> > 2.6.24 - 2.6.25.3 has not been tested
Has this been seen on non-UML?
Jeff
--
Work email - jdike at linux dot intel dot com
next prev parent reply other threads:[~2008-06-02 1:06 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 [this message]
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
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=20080602010546.GA8578@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 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.