From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
David Woodhouse <dwmw@amazon.co.uk>,
Arjan van de Ven <arjan@linux.intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Andi Kleen <ak@linux.intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
Jiri Kosina <jikos@kernel.org>,
Greg Kroah-Hartman <gregkh@linux-foundation.org>,
Paul Turner <pjt@google.com>
Subject: Re: x86: Meltdown/Spectre_v2 status
Date: Fri, 12 Jan 2018 16:48:14 -0600 [thread overview]
Message-ID: <20180112224814.q722naei5qs76bam@treble> (raw)
In-Reply-To: <alpine.DEB.2.20.1801122200000.2371@nanos>
On Fri, Jan 12, 2018 at 10:44:48PM +0100, Thomas Gleixner wrote:
> Folks!
>
> After 10 days of frenzy following the disclosure of the mess, I'm at a
> point where I think that the current set which we have in Linus tree and
> the pending patches in tip:x86/pti plus one not yet applied patch (RSB on
> context switch) have reached a state where the main targets are covered
> even on skylake:
>
> 1) Meltdown is addressed
> 2) Retpoline mostly covered if we have working compilers some day
> 3) RSB after vmexit and on context switch (pending)
>
> plus the infrastructure and basic building blocks are in place.
>
> That's what is going to be in 4.15 (unless Linus goes berserk on the pull
> requests)
And for those who are curious (I was) it looks like the BPF variant 1
fix has already been merged into Linus' tree.
> and next week should be focussed on eventual fallout, fixes and
> small corrections here and there. Also to spend some time on taming the
> backlog of our inboxes a bit. There is also stuff happening outside of this
> which needs our attention and care.
>
> I want to say thanks to everyone involved and I want to apologize if I went
> overboard or offended someone in the course of the discussions.
>
> Surely we all know there is room for improvements, but we also have reached
> a state where the remaining issues are not longer to be treated in full
> emergency and panic mode. We're good now, but not perfect.
>
> The further RSB vs. IBRS discussion has to be settled in the way we
> normally work. We need full documentation, proper working micro code and
> actual comparisons of the two approaches vs. performance, coverage of
> attack vectors and code complexity/ugliness.
>
> We all are exhausted and at our limits and I think we can agree that having
> the most problematic stuff covered is the right point to calm down and put
> the heads back on the chickens. Take a break and have a few drinks at least
> over the weekend!
>
> To be honest the last 10 days were more horrible than the whole PTI work
> due to lack of documentation, 12 different opinions when asking 8 people
> (why does this have a lawyer smell?) and an amazing amount of half baken
> and hastily cobbled together crap.
>
> Please lets stop this and return to normality now.
Amen.
Thomas, amazing job distilling some sanity out of the pandemonium.
For future patch submissions, I would ask everyone to at least add
x86@kernel.org to To: or Cc: (along with lkml). It's not only good
etiquette to help the x86 maintainers, but it also gives those us not
directly on Cc: a way to filter the patches into our inboxes.
--
Josh
next prev parent reply other threads:[~2018-01-12 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 21:44 x86: Meltdown/Spectre_v2 status Thomas Gleixner
2018-01-12 22:48 ` Josh Poimboeuf [this message]
2018-01-13 11:55 ` Woodhouse, David
2018-01-15 14:28 ` Josh Poimboeuf
2018-01-15 14:57 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180112224814.q722naei5qs76bam@treble \
--to=jpoimboe@redhat.com \
--cc=ak@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linux-foundation.org \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).