All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: stable@kernel.org, LKML <linux-kernel@vger.kernel.org>,
	stable-review@kernel.org
Subject: Re: [PATCH] Fix 'flush_old_exec()/setup_new_exec()' split
Date: Thu, 04 Feb 2010 08:29:34 +0000	[thread overview]
Message-ID: <1265272174.2952.20.camel@localhost> (raw)
In-Reply-To: <alpine.LFD.2.00.1002032135380.3707@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]

On Wed, 2010-02-03 at 21:39 -0800, Linus Torvalds wrote:
> 
> On Thu, 4 Feb 2010, Ben Hutchings wrote:
> > 
> > I'm using Debian i386 (i.e. 32-bit userland) with a 64-bit kernel.
> > After applying commit 221af7f to Debian's kernel source (approximately
> > equivalent to 2.6.32.7), the kernel fails to exec init.  After commit
> > 7ab02af it can exec init but that immediately segfaults:
> 
> It sounds like you have picked individual commits.

Yes - I'm one of the kernel package maintainers and we're sticking with
2.6.32-stable.

> But you don't mention commit 05d43ed8a, which is also a required part of 
> the series.
> 
> So you _should_ have a combination of
>  - 221af7f87 ("Split 'flush_old_exec' into two functions")
>  - 05d43ed8a ("x86: get rid of the insane TIF_ABI_PENDING bit")
>  - 7ab02af42 ("Fix 'flush_old_exec()/setup_new_exec()' split")
> 
> (and there are also additional sparc/ppc versions of that TIF_ABI_PENDING 
> bit removal, but they shouldn't matter on your system)

Thanks.  If all the necessary patches are all in the stable queue then
we can pick them from there.

Ben.

-- 
Ben Hutchings
friends: People who know you well, but like you anyway.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2010-02-04  8:29 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 [this message]
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
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=1265272174.2952.20.camel@localhost \
    --to=ben@decadent.org.uk \
    --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.