From: Sven Joachim <svenjoac@gmx.de>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Greg KH <greg@kroah.com>,
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 11:23:26 +0100 [thread overview]
Message-ID: <87iqachtgh.fsf@turtle.gmx.de> (raw)
In-Reply-To: <20100204222522.GF20379@decadent.org.uk> (Ben Hutchings's message of "Thu, 4 Feb 2010 22:25:22 +0000")
On 2010-02-04 23:25 +0100, Ben Hutchings wrote:
> In a Debian initramfs, /init is a script interpreted by /bin/sh.
Yes, I tested without an initramfs though. The crash happens actually
before init is run.
> I've now tested i386 userland on an x86_64 kernel with all the relevant
> patches on top of 2.6.32.7:
>
> fdpic-respect-pt_gnu_stack-exec-protection-markings-when-creating-nommu-stack.patch
> split-flush_old_exec-into-two-functions.patch
> sparc-tif_abi_pending-bit-removal.patch
> x86-get-rid-of-the-insane-tif_abi_pending-bit.patch
> fix-flush_old_exec-setup_new_exec-split.patch
> powerpc-tif_abi_pending-bit-removal.patch
>
> This works perfectly, so far as I can see.
It seems so. The faulty patch is actually the cherry-pick of commit
28f6aeea (net: restore ip source validation), reverting that leads to a
kernel that runs fine. And this has nothing to do with 64-bit vs
32-bit.
Sven
next prev parent reply other threads:[~2010-02-05 10:23 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
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 [this message]
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=87iqachtgh.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.