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
include
Kconfig -rw-r--r-- 2.0 KB
Makefile -rw-r--r-- 586 bytes
Makefile.boot -rw-r--r-- 256 bytes
at91rm9200.c -rw-r--r-- 1.1 KB
at91sam9.c -rw-r--r-- 3.4 KB
generic.h -rw-r--r-- 1014 bytes
pm.c -rw-r--r-- 10.7 KB
pm.h -rw-r--r-- 749 bytes
pm_suspend.S -rw-r--r-- 6.7 KB
sam9_smc.c -rw-r--r-- 3.6 KB
sam9_smc.h -rw-r--r-- 334 bytes
sama5.c -rw-r--r-- 1.9 KB
soc.c -rw-r--r-- 2.3 KB
soc.h -rw-r--r-- 2.2 KB

back to top