linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Woodhouse, David" <dwmw@amazon.co.uk>
To: "tglx@linutronix.de" <tglx@linutronix.de>,
	"jpoimboe@redhat.com" <jpoimboe@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"arjan@linux.intel.com" <arjan@linux.intel.com>,
	"mingo@kernel.org" <mingo@kernel.org>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"tim.c.chen@linux.intel.com" <tim.c.chen@linux.intel.com>,
	"ak@linux.intel.com" <ak@linux.intel.com>,
	"pjt@google.com" <pjt@google.com>, "bp@alien8.de" <bp@alien8.de>,
	"dave.hansen@intel.com" <dave.hansen@intel.com>,
	"jikos@kernel.org" <jikos@kernel.org>,
	"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
	"gregkh@linux-foundation.org" <gregkh@linux-foundation.org>
Subject: Re: x86: Meltdown/Spectre_v2 status
Date: Sat, 13 Jan 2018 11:55:17 +0000	[thread overview]
Message-ID: <1515844512.22302.543.camel@amazon.co.uk> (raw)
In-Reply-To: <20180112224814.q722naei5qs76bam@treble>


[-- Attachment #1.1: Type: text/plain, Size: 1533 bytes --]

On Fri, 2018-01-12 at 16:48 -0600, Josh Poimboeuf wrote:
> >   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)

To be clear: This doesn't include IBPB and thus userspace processes
(and VM guests) are not protected from each other.

But the attacks there are extremely hard to pull off, and I think we
can live with that in the short term. IBPB does need to be next, but I
think we're entirely correct to proceed without it for now. I just want
to make sure we're clear about the status.

> And for those who are curious (I was) it looks like the BPF variant 1
> fix has already been merged into Linus' tree.

Great. I was going to check on that too.

> Thomas, amazing job distilling some sanity out of the pandemonium.

Indeed. Thank you, Thomas.

FWIW we've done a backport of the sysfs/vulnerability and retpoline
parts to 4.9, including cherry-picking a few earlier needed commits:
http://git.infradead.org/retpoline-stable.git/shortlog/refs/heads/linux-4.9.y

Josh, I'd very much appreciate your eyes on my objtool-related
backports — both your retpoline-specific patches, as well as the
.discard.* bits they depended on. Thanks.

Bringing ASM_CALL_CONSTRAINT in as-is seemed like the same thing to do
too.

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5210 bytes --]

[-- Attachment #2.1: Type: text/plain, Size: 197 bytes --]




Amazon Web Services UK Limited. Registered in England and Wales with registration number 08650665 and which has its registered office at 60 Holborn Viaduct, London EC1A 2FD, United Kingdom.

[-- Attachment #2.2: Type: text/html, Size: 197 bytes --]

  reply	other threads:[~2018-01-13 11:55 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
2018-01-13 11:55   ` Woodhouse, David [this message]
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=1515844512.22302.543.camel@amazon.co.uk \
    --to=dwmw@amazon.co.uk \
    --cc=ak@linux.intel.com \
    --cc=arjan@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=gregkh@linux-foundation.org \
    --cc=jikos@kernel.org \
    --cc=jpoimboe@redhat.com \
    --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).