summaryrefslogtreecommitdiffstats
path: root/crypto/xts.c
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2018-01-03 15:57:59 +0100
committerThomas Gleixner <tglx@linutronix.de>2018-01-03 15:57:59 +0100
commit52994c256df36fda9a715697431cba9daecb6b11 (patch)
treec446672f16e816c3221f2cfff71cd988dc8c78ae /crypto/xts.c
parent694d99d40972f12e59a3696effee8a376b79d7c8 (diff)
downloadlinux-52994c256df36fda9a715697431cba9daecb6b11.tar.bz2
x86/pti: Make sure the user/kernel PTEs match
Meelis reported that his K8 Athlon64 emits MCE warnings when PTI is enabled: [Hardware Error]: Error Addr: 0x0000ffff81e000e0 [Hardware Error]: MC1 Error: L1 TLB multimatch. [Hardware Error]: cache level: L1, tx: INSN The address is in the entry area, which is mapped into kernel _AND_ user space. That's special because we switch CR3 while we are executing there. User mapping: 0xffffffff81e00000-0xffffffff82000000 2M ro PSE GLB x pmd Kernel mapping: 0xffffffff81000000-0xffffffff82000000 16M ro PSE x pmd So the K8 is complaining that the TLB entries differ. They differ in the GLB bit. Drop the GLB bit when installing the user shared mapping. Fixes: 6dc72c3cbca0 ("x86/mm/pti: Share entry text PMD") Reported-by: Meelis Roos <mroos@linux.ee> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Tested-by: Meelis Roos <mroos@linux.ee> Cc: Borislav Petkov <bp@alien8.de> Cc: Tom Lendacky <thomas.lendacky@amd.com> Cc: stable@vger.kernel.org Link: https://lkml.kernel.org/r/alpine.DEB.2.20.1801031407180.1957@nanos
Diffstat (limited to 'crypto/xts.c')
0 files changed, 0 insertions, 0 deletions