From: Ben Hutchings <ben@decadent.org.uk>
To: stable@kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.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 04:02:54 +0000 [thread overview]
Message-ID: <1265256174.2952.11.camel@localhost> (raw)
In-Reply-To: <1265245849.3362.1.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1884 bytes --]
On Thu, 2010-02-04 at 01:10 +0000, Ben Hutchings wrote:
> Commit 7ab02af428c2d312c0cf8fb0b01cc1eb21131a3d upstream fixes a
> regression caused by 221af7f87b97431e3ee21ce4b0e77d5411cf1549.
Having said that, it doesn't really fix it for me.
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:
[ 0.684493] init[1]: segfault at 6d241850 ip 000000006d241850 sp 00000000403fca30 error 14
[ 0.686204] Kernel panic - not syncing: Attempted to kill init!
[ 0.687081] Pid: 1, comm: init Not tainted 2.6.32-2-amd64 #1
[ 0.687968] Call Trace:
[ 0.688716] [<ffffffff812e8c21>] ? panic+0x86/0x141
[ 0.689540] [<ffffffff8104a63a>] ? __cond_resched+0x1d/0x26
[ 0.690390] [<ffffffff81056aed>] ? exit_ptrace+0x30/0x126
[ 0.692344] [<ffffffff81050cd3>] ? do_exit+0x72/0x6b5
[ 0.693261] [<ffffffff8105138c>] ? do_group_exit+0x76/0x9d
[ 0.694203] [<ffffffff8105da4c>] ? get_signal_to_deliver+0x310/0x33c
[ 0.695719] [<ffffffff8101000f>] ? do_notify_resume+0x87/0x73f
[ 0.696754] [<ffffffff81188de8>] ? __down_read_trylock+0x3e/0x44
[ 0.697717] [<ffffffff81188f75>] ? __up_read+0x13/0x8e
[ 0.698748] [<ffffffff8101159c>] ? retint_signal+0x48/0x8c
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 --]
next parent reply other threads:[~2010-02-04 4:03 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 ` Ben Hutchings [this message]
2010-02-04 5:39 ` [PATCH] Fix 'flush_old_exec()/setup_new_exec()' split 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
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=1265256174.2952.11.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).