Revision dbe3ed1c078c193be34326728d494c5c4bc115e2 authored by Linus Torvalds on 19 September 2007, 18:37:14 UTC, committed by Linus Torvalds on 19 September 2007, 18:37:14 UTC
Randy Dunlap noticed an interesting "crashme" behaviour on his dual
Prescott Xeon setup, where he gets page faults with the error code
having a zero "user" bit, but the register state points back to user
mode.

This may be a CPU microcode buglet triggered by some strange instruction
pattern that crashme generates, and loading a microcode update seems to
possibly have fixed it.

Regardless, we really should trust the register state more than the
error code, since it's really the register state that determines whether
we can actually send a signal, or whether we're in kernel mode and need
to oops/kill the process in the case of a page fault.

Cc: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
1 parent 4f01a75
History
File Mode Size
Kconfig -rw-r--r-- 2.0 KB
Kconfig.iosched -rw-r--r-- 1.9 KB
Makefile -rw-r--r-- 382 bytes
as-iosched.c -rw-r--r-- 37.8 KB
blktrace.c -rw-r--r-- 12.5 KB
bsg.c -rw-r--r-- 22.2 KB
cfq-iosched.c -rw-r--r-- 53.9 KB
deadline-iosched.c -rw-r--r-- 11.6 KB
elevator.c -rw-r--r-- 25.1 KB
genhd.c -rw-r--r-- 19.6 KB
ioctl.c -rw-r--r-- 7.4 KB
ll_rw_blk.c -rw-r--r-- 105.6 KB
noop-iosched.c -rw-r--r-- 2.6 KB
scsi_ioctl.c -rw-r--r-- 16.9 KB

back to top