Re: [tip:x86/vdso] x86/vdso32/syscall.S: Do not load __USER32_DS to %ss
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:x86/vdso] x86/vdso32/syscall.S: Do not load __USER32_DS to %ss
- From: Borislav Petkov <bp@xxxxxxxxx>
- Date: Thu, 23 Apr 2015 11:56:31 +0200
- Cc: Brian Gerst <brgerst@xxxxxxxxx>, Steven Rostedt <rostedt@xxxxxxxxxxx>, Oleg Nesterov <oleg@xxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Andy Lutomirski <luto@xxxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Andy Lutomirski <luto@xxxxxxxxxx>, Will Drewry <wad@xxxxxxxxxxxx>, Frédéric Weisbecker <fweisbec@xxxxxxxxx>, Alexei Starovoitov <ast@xxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Kees Cook <keescook@xxxxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <5538B978.3060307@redhat.com>
- User-agent: Mutt/1.5.23 (2014-03-12)
On Thu, Apr 23, 2015 at 11:20:56AM +0200, Denys Vlasenko wrote:
> * what if %ss before syscall was NOT the usual value of 0x2b, but some
> other segment, not the typical 0-base, 0xffffffff limit 32-bit expand-up one?
> Not restoring proper %ss would not go well.
> [but then, Intel CPUs work, and old code worked....]
Have we run the exact same reproducer on Intel already?
Brian, can you run the same thing on an Intel box, if you haven't done
so already?
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]
