From: Ben Hutchings <ben@decadent.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sven Joachim <svenjoac@gmx.de>, 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: Thu, 4 Feb 2010 22:25:22 +0000 [thread overview]
Message-ID: <20100204222522.GF20379@decadent.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.1002041102530.3707@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
On Thu, 2010-02-04 at 11:11 -0800, Linus Torvalds wrote:
>
> On Thu, 4 Feb 2010, Sven Joachim wrote:
> >
> > It seems they are all there, but on my system with 64-bit kernel and
> > 32-bit userland, 2.6.32.8-rc1 still panics in the way noticed by Ben.
>
> Ok. Greg - please skip these patches from stable for now. I'll try to
> figure out what's up.
>
> Sven/Ben: is /sbin/init (or wherever debian puts it) a regular ELF file?
> Shared libraries? Anything at all special about it? I wonder why it seems
> to have issues, when other 32-bit programs don't.
In a Debian initramfs, /init is a script interpreted by /bin/sh.
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.
Ben.
--
Ben Hutchings
friends: People who know you well, but like you anyway.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2010-02-04 22:26 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 [this message]
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=20100204222522.GF20379@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-review@kernel.org \
--cc=stable@kernel.org \
--cc=svenjoac@gmx.de \
--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.