diff options
author | Chuck Ebbert <cebbert@redhat.com> | 2007-08-10 22:31:11 +0200 |
---|---|---|
committer | Linus Torvalds <torvalds@woody.linux-foundation.org> | 2007-08-11 15:58:14 -0700 |
commit | 3dab307e527f2a9bbb4f9d00240374bb93d1945f (patch) | |
tree | 3e9a83d6cc1cee1dcfedff700c0b4aeebaa2f8d5 /Documentation/locks.txt | |
parent | 5fe4486c79cdc8dbbb2a9c3f884a5ad0830a5a23 (diff) | |
download | kernel-crypto-3dab307e527f2a9bbb4f9d00240374bb93d1945f.tar.gz kernel-crypto-3dab307e527f2a9bbb4f9d00240374bb93d1945f.tar.xz kernel-crypto-3dab307e527f2a9bbb4f9d00240374bb93d1945f.zip |
i386: Fix double fault handler
The new percpu code has apparently broken the doublefault handler
when CONFIG_DEBUG_SPINLOCK is set. Doublefault is handled by
a hardware task, making the check
SPIN_BUG_ON(lock->owner == current, lock, "recursion");
fault because it uses the FS register to access the percpu data
for current, and that register is zero in the new TSS. (The trace
I saw was on 2.6.20 where it was GS, but it looks like this will
still happen with FS on 2.6.22.)
Initializing FS in the doublefault_tss should fix it.
AK: Also fix broken ptr_ok() and turn printks into KERN_EMERG
AK: And add a PANIC prefix to make clear the system will hang
AK: (e.g. x86-64 will recover)
Signed-off-by: Chuck Ebbert <cebbert@redhat.com>
Signed-off-by: Andi Kleen <ak@suse.de>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/locks.txt')
0 files changed, 0 insertions, 0 deletions