Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 27 Jan 2018 10:52:27 -0800
From: Linus Torvalds <>
To: Dan Williams <>
Cc: Thomas Gleixner <>, Mark Rutland <>, 
	Cyril Novikov <>, Kernel Hardening <>, 
	Peter Zijlstra <>, Catalin Marinas <>, 
	Will Deacon <>, "H. Peter Anvin" <>, Jiri Slaby <>, 
	Elena Reshetova <>, linux-arch <>, 
	Andi Kleen <>, Jonathan Corbet <>, 
	"the arch/x86 maintainers" <>, Russell King <>, Ingo Molnar <>, 
	Andrew Honig <>, Alan Cox <>, 
	Tom Lendacky <>, Kees Cook <>, 
	Al Viro <>, Andy Lutomirski <>, 
	Jim Mattson <>, Christian Lamparter <>, 
	Greg Kroah-Hartman <>, 
	Linux Wireless List <>, Paolo Bonzini <>, 
	Johannes Berg <>, "David S. Miller" <>
Subject: Re: [PATCH v5 00/12] spectre variant1 mitigations for tip/x86/pti

On Fri, Jan 26, 2018 at 11:55 PM, Dan Williams <> wrote:
> Here's another spin of the spectre-v1 mitigations for 4.16.

I see nothing really objectionable here.

And unlike Spectre-v2 and Meltdown, I expect Spectre-v1 to be with us
for a long time. It's not a "CPU did a bad job with checking the
cached information it had" (whether it be from the TLB, BTB or RSB),
it's pretty fundamental to just regular conditional branch prediction.

So ack from me, and I don't expect this to be behind any config options.

I still haven't really seen any numbers for this, but I _assume_ it's
basically not measurable.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.