You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Linus Torvalds dbe3ed1c07 x86-64: page faults from user mode are always user faults ... 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>		18 years ago
..
Makefile	…
extable.c	…
fault.c	x86-64: page faults from user mode are always user faults	18 years ago
init.c	Revert most of "x86: Fix alternatives and kprobes to remap write-protected kernel text"	18 years ago
ioremap.c	…
k8topology.c	x86_64: make k8topology multi-core aware	18 years ago
mmap.c	…
numa.c	…
pageattr.c	x86: Disable CLFLUSH support again	18 years ago
srat.c	…