LKML Archive on
help / color / mirror / Atom feed
From: Chuck Ebbert <>
To: linux-kernel <>
Cc: Ingo Molnar <>, Gerd Hoffmann <>
Subject: The SMP alternatives code breaks exception fixup?
Date: Mon, 21 Jan 2008 15:47:50 -0500	[thread overview]
Message-ID: <> (raw)

Looking at the oops report from this bug:


It was an unhandled page fault (protection violation.)

I tracked it down to the cmpxchg in this code:

         __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.

             reply	other threads:[~2008-01-21 20:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 20:47 Chuck Ebbert [this message]
2008-01-21 21:25 ` The SMP alternatives code breaks exception fixup? Chuck Ebbert
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).