summaryrefslogtreecommitdiffstats
path: root/firmware
diff options
context:
space:
mode:
authorAndy Lutomirski <luto@kernel.org>2018-06-26 22:17:17 -0700
committerIngo Molnar <mingo@kernel.org>2018-06-27 09:36:56 +0200
commitec348020566009d3da9b99f07c05814d13969c78 (patch)
tree14c164f98353e3e4fa1aa9f959448e423ef82b14 /firmware
parent22cd978e598618e82c3c3348d2069184f6884182 (diff)
downloadlinux-stable-ec348020566009d3da9b99f07c05814d13969c78.tar.gz
linux-stable-ec348020566009d3da9b99f07c05814d13969c78.tar.bz2
linux-stable-ec348020566009d3da9b99f07c05814d13969c78.zip
selftests/x86/sigreturn/64: Fix spurious failures on AMD CPUs
When I wrote the sigreturn test, I didn't realize that AMD's busted IRET behavior was different from Intel's busted IRET behavior: On AMD CPUs, the CPU leaks the high 32 bits of the kernel stack pointer to certain userspace contexts. Gee, thanks. There's very little the kernel can do about it. Modify the test so it passes. Signed-off-by: Andy Lutomirski <luto@kernel.org> Cc: Borislav Petkov <bp@alien8.de> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: http://lkml.kernel.org/r/86e7fd3564497f657de30a36da4505799eebef01.1530076529.git.luto@kernel.org Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions