From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965331AbeALWsU (ORCPT + 1 other); Fri, 12 Jan 2018 17:48:20 -0500 Received: from mx1.redhat.com ([209.132.183.28]:38840 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965236AbeALWsS (ORCPT ); Fri, 12 Jan 2018 17:48:18 -0500 Date: Fri, 12 Jan 2018 16:48:14 -0600 From: Josh Poimboeuf To: Thomas Gleixner Cc: LKML , Linus Torvalds , Ingo Molnar , Borislav Petkov , Peter Zijlstra , David Woodhouse , Arjan van de Ven , Dave Hansen , Andi Kleen , Tom Lendacky , Tim Chen , Jiri Kosina , Greg Kroah-Hartman , Paul Turner Subject: Re: x86: Meltdown/Spectre_v2 status Message-ID: <20180112224814.q722naei5qs76bam@treble> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0.1 (2016-04-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Fri, 12 Jan 2018 22:48:18 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: 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