linux-kernel - Re: [PATCH 1/5] x86/entry/32: Clean up enable_sep

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] [day] [month] [year] [list]

Message-ID: <CA+55aFz3d38NN4NU+1+ZjNLnb-YN9Dob7vm73ABEosxe9jq=NQ@mail.gmail.com>
Date:	Thu, 23 Jul 2015 11:50:04 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	Brian Gerst <brgerst@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Andy Lutomirski <luto@...nel.org>, X86 ML <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Willy Tarreau <w@....eu>, Borislav Petkov <bp@...en8.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH 1/5] x86/entry/32: Clean up enable_sep_cpu to prepare for
 64-bit merge

On Thu, Jul 23, 2015 at 11:42 AM, Andy Lutomirski <luto@...capital.net> wrote:
>
> On third thought, no v2.  It's *64-bit* CPUs that might want the
> _safe.  We aren't currently checking SEP.  Maybe there's a non-SEP AMD
> CPU and we never noticed because SEP was never useful on AMD 64-bit
> CPUs.

I don't see the downside of using the safe version unconditionally. No
need to worry about any corner cases.

                  Linus
--
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/