Re: [stable] [PATCH] Fix 'flush_old_exec()/setup_new_exec()' split

[Greg KH]

On Thu, Feb 04, 2010 at 07:46:30PM +0100, Sven Joachim wrote:
> On 2010-02-04 15:38 +0100, Greg KH wrote:
> 
> > On Thu, Feb 04, 2010 at 08:29:34AM +0000, Ben Hutchings wrote:
> >> 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.
> >
> > They should all be there already, if not, please let me know.
> 
> 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.

Does 2.6.33-rc6 also cause you the same problem?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/