x86/smep: Be more informative when signalling an SMEP fault
authorJiri Kosina <jkosina@suse.cz>
Tue, 10 Jun 2014 20:49:31 +0000 (22:49 +0200)
committerH. Peter Anvin <hpa@linux.intel.com>
Thu, 12 Jun 2014 00:55:30 +0000 (17:55 -0700)
commiteff50c347fcc8feeb8c1723c23c89aba67c60263
treeb6c7182ebd6f8b4c6eb8301cb9cd485f3f6f0cfc
parented81e780a7dd5698a986f246fad6a1d8d0b6f9ce
x86/smep: Be more informative when signalling an SMEP fault

If pagefault triggers due to SMEP triggering, it can't be really easily
distinguished from any other oops-causing pagefault, which might lead to quite
some confusion when trying to understand the reason for the oops.

Print an explanatory message in case the fault happened during instruction
fetch for _PAGE_USER page which is present and executable on SMEP-enabled CPUs.

This is consistent with what we are doing for NX already; in addition to
immediately seeing from the oops what might be happening, it can even easily
give a good indication to sysadmins who are carefully monitoring their kernel
logs that someone might be trying to pwn them.

Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Link: http://lkml.kernel.org/r/alpine.LNX.2.00.1406102248490.1321@pobox.suse.cz
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
arch/x86/mm/fault.c