x86, smap: smap_violation() is bogus if CONFIG_X86_SMAP is off
authorH. Peter Anvin <hpa@linux.intel.com>
Thu, 13 Feb 2014 15:46:04 +0000 (07:46 -0800)
committerH. Peter Anvin <hpa@linux.intel.com>
Thu, 13 Feb 2014 16:40:52 +0000 (08:40 -0800)
commit4640c7ee9b8953237d05a61ea3ea93981d1bc961
tree580aa78183348a9cfcea51a50b1cc4e8ef5a309f
parent03bbd596ac04fef47ce93a730b8f086d797c3021
x86, smap: smap_violation() is bogus if CONFIG_X86_SMAP is off

If CONFIG_X86_SMAP is disabled, smap_violation() tests for conditions
which are incorrect (as the AC flag doesn't matter), causing spurious
faults.

The dynamic disabling of SMAP (nosmap on the command line) is fine
because it disables X86_FEATURE_SMAP, therefore causing the
static_cpu_has() to return false.

Found by Fengguang Wu's test system.

[ v3: move all predicates into smap_violation() ]
[ v2: use IS_ENABLED() instead of #ifdef ]

Reported-by: Fengguang Wu <fengguang.wu@intel.com>
Link: http://lkml.kernel.org/r/20140213124550.GA30497@localhost
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Cc: <stable@vger.kernel.org> # v3.7+
arch/x86/mm/fault.c