From: Chuck Ebbert <cebbert@redhat.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: The SMP alternatives code breaks exception fixup?
Date: Mon, 21 Jan 2008 16:25:14 -0500 [thread overview]
Message-ID: <47950DBA.9080906@redhat.com> (raw)
In-Reply-To: <479504F6.4080005@redhat.com>
On 01/21/2008 03:47 PM, Chuck Ebbert wrote:
> Looking at the oops report from this bug:
>
> [bugzilla] https://bugzilla.redhat.com/show_bug.cgi?id=429412
> [oops] https://bugzilla.redhat.com/attachment.cgi?id=292260
>
> It was an unhandled page fault (protection violation.)
>
> I tracked it down to the cmpxchg in this code:
>
> include/asm-x86/futex_32.h::futex_atomic_cmpxchg_inatomic()
> __asm__ __volatile__(
> "1: " LOCK_PREFIX "cmpxchgl %3, %1 \n"
> "2: .section .fixup, \"ax\" \n"
> "3: mov %2, %0 \n"
> " jmp 2b \n"
> " .previous \n"
> " .section __ex_table, \"a\" \n"
> " .align 8 \n"
> " .long 1b,3b \n"
> " .previous \n"
>
> There is a fixup, so this should never happen. But the lock instruction
> was replaced with a nop by the altinstruction code, and that makes the fixup
> address wrong. AFAICT we don't fix up the exception table when we replace
> a lock with a nop, which makes the fixup table point to the nop instead
> of the cmpxchg instruction and causes us to miss the fixup.
>
The bug reporter has confirmed that booting with "noreplace-smp" prevents
the kernel oops.
next prev parent reply other threads:[~2008-01-21 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 20:47 The SMP alternatives code breaks exception fixup? Chuck Ebbert
2008-01-21 21:25 ` Chuck Ebbert [this message]
2008-01-22 5:26 ` Andi Kleen
2008-01-22 12:35 ` Thomas Gleixner
2008-01-22 20:19 ` Chuck Ebbert
2008-02-06 23:10 ` [stable] " Greg KH
2008-02-06 23:36 ` Linus Torvalds
2008-02-06 23:43 ` Ingo Molnar
2008-02-07 0:00 ` Greg KH
2008-02-07 6:55 ` Greg KH
2008-02-07 12:16 ` Thomas Gleixner
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=47950DBA.9080906@redhat.com \
--to=cebbert@redhat.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.