linux-kernel - Re: [PATCH] x86/entry/32: Initialize ss1 (SYSENTER

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMzpN2hE25uPp8yr1RtK-gwt0d__aBkrw3-O4HfNFgdYs9gBuQ@mail.gmail.com>
Date:	Thu, 23 Jul 2015 15:03:04 -0400
From:	Brian Gerst <brgerst@...il.com>
To:	Andy Lutomirski <luto@...nel.org>
Cc:	X86 ML <x86@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>, Willy Tarreau <w@....eu>,
	Borislav Petkov <bp@...en8.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] x86/entry/32: Initialize ss1 (SYSENTER_CS shadow) even on
 non-SEP CPUs

On Thu, Jul 23, 2015 at 2:56 PM, Andy Lutomirski <luto@...nel.org> wrote:
> native_load_sp0 relies on this.  I'm not sure why we haven't seen
> reports of crashes.  Maybe no one tests new kernels on non-SEP CPUs.

It's already statically initialized in cpu_tss.

--
Brian Gerst
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/