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
00-INDEX -rw-r--r-- 818 bytes
biodoc.txt -rw-r--r-- 52.8 KB
biovecs.txt -rw-r--r-- 5.5 KB
capability.txt -rw-r--r-- 618 bytes
cfq-iosched.txt -rw-r--r-- 12.5 KB
cmdline-partition.txt -rw-r--r-- 1.3 KB
data-integrity.txt -rw-r--r-- 11.9 KB
deadline-iosched.txt -rw-r--r-- 2.8 KB
ioprio.txt -rw-r--r-- 4.6 KB
null_blk.txt -rw-r--r-- 2.5 KB
queue-sysfs.txt -rw-r--r-- 4.8 KB
request.txt -rw-r--r-- 2.0 KB
stat.txt -rw-r--r-- 3.2 KB
switching-sched.txt -rw-r--r-- 1.4 KB
writeback_cache_control.txt -rw-r--r-- 3.8 KB

back to top