From: Sven Joachim <svenjoac@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg KH <greg@kroah.com>, Ben Hutchings <ben@decadent.org.uk>,
stable-review@kernel.org, stable@kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [stable] [PATCH] Fix 'flush_old_exec()/setup_new_exec()' split
Date: Fri, 05 Feb 2010 06:44:21 +0100 [thread overview]
Message-ID: <87eil0dyoa.fsf@turtle.gmx.de> (raw)
In-Reply-To: <alpine.LFD.2.00.1002041135110.3707@localhost.localdomain> (Linus Torvalds's message of "Thu, 4 Feb 2010 11:37:24 -0800 (PST)")
On 2010-02-04 20:37 +0100, Linus Torvalds wrote:
> Ok, then that's just really odd. I don't think there are any other changes
> in this area, and the whole init problem sure as hell smells like execve
> setup problems. And afaik, 2.6.32.8-rc1 should have all the commits from
> current -git.
>
> Maybe we're looking at a separate issue after all.
Possibly, because a 32-bit 2.6.32.8-rc1 kernel also panics very early.
Sven
next prev parent reply other threads:[~2010-02-05 5:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1265245849.3362.1.camel@localhost>
2010-02-04 4:02 ` [PATCH] Fix 'flush_old_exec()/setup_new_exec()' split Ben Hutchings
2010-02-04 5:39 ` Linus Torvalds
2010-02-04 8:29 ` Ben Hutchings
2010-02-04 14:38 ` [stable] " Greg KH
2010-02-04 18:46 ` Sven Joachim
2010-02-04 18:57 ` Greg KH
2010-02-04 19:32 ` Sven Joachim
2010-02-04 19:37 ` Linus Torvalds
2010-02-05 5:44 ` Sven Joachim [this message]
2010-02-06 8:49 ` Greg KH
2010-02-06 9:21 ` Sven Joachim
2010-02-06 9:31 ` [Stable-review] " Willy Tarreau
2010-02-06 9:55 ` [stable] [Stable-review] " Greg KH
2010-02-04 19:11 ` [stable] " Linus Torvalds
2010-02-04 19:45 ` Sven Joachim
2010-02-04 19:54 ` Linus Torvalds
2010-02-04 22:25 ` Ben Hutchings
2010-02-05 10:23 ` Sven Joachim
2010-02-04 15:57 ` Linus Torvalds
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=87eil0dyoa.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=ben@decadent.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-review@kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
/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.