Revision 61f01dd941ba9e06d2bf05994450ecc3d61b6b8b authored by Andy Lutomirski on 26 April 2015, 23:47:59 UTC, committed by Linus Torvalds on 27 April 2015, 00:57:38 UTC
AMD CPUs don't reinitialize the SS descriptor on SYSRET, so SYSRET with
SS == 0 results in an invalid usermode state in which SS is apparently
equal to __USER_DS but causes #SS if used.

Work around the issue by setting SS to __KERNEL_DS __switch_to, thus
ensuring that SYSRET never happens with SS set to NULL.

This was exposed by a recent vDSO cleanup.

Fixes: e7d6eefaaa44 x86/vdso32/syscall.S: Do not load __USER32_DS to %ss
Signed-off-by: Andy Lutomirski <luto@kernel.org>
Cc: Peter Anvin <hpa@zytor.com>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Denys Vlasenko <vda.linux@googlemail.com>
Cc: Brian Gerst <brgerst@gmail.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
1 parent 1190944
History
File Mode Size
configs
drivers
include
kernel
os-Linux
scripts
.gitignore -rw-r--r-- 53 bytes
Kconfig.char -rw-r--r-- 4.4 KB
Kconfig.common -rw-r--r-- 722 bytes
Kconfig.debug -rw-r--r-- 997 bytes
Kconfig.net -rw-r--r-- 8.5 KB
Kconfig.rest -rw-r--r-- 291 bytes
Kconfig.um -rw-r--r-- 3.9 KB
Makefile -rw-r--r-- 5.0 KB
Makefile-os-Linux -rw-r--r-- 235 bytes
Makefile-skas -rw-r--r-- 290 bytes

back to top