From: Jon Masters <jcm@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v5 0/8] L1TFv4 5
Date: Thu, 24 May 2018 10:12:41 -0400 [thread overview]
Message-ID: <935c8f01-09b2-260f-78ac-32f62ab3b8de@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.21.999.1805231524460.32557@i7.lan>
[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]
On 05/23/2018 06:28 PM, speck for Linus Torvalds wrote:
>
>
> On Thu, 24 May 2018, speck for Jiri Kosina wrote:
>>>
>>> Btw., what's the expected release date for this issue?
>>
>> 2018-08-14 AFAIK (including all the virtualization implications, and
>> together with the unrelated lazy FPU switching thing).
There's an accepted paper at <conf removed> in August which will
disclose a separate attack (also covered by the Intel letter) from which
this can easily be inferred once public. There is some risk from that
paper ahead of time but some effort has been placed into isolating it
until the conference. Unfortunately, that's a pretty hard deadline.
> Christ. And people don't think it will leak before that, with people
> already sniffing around it?
Which is why we need to be very careful with this list and such (and why
I sent mail about it, etc.). On our end, we consider containment failure
highly likely, but we are hoping to make it until Aug due to the immense
lift required from many third parties, such as all the cloud vendors. I
would really reinforce the need for us to be very careful with this one.
> I was hoping that Intel would have Coffee Lake out and this *fixed* by
> August, rather than the whole disclosure being that late. It damn well
> should be one single little 'and' to turn all non-P gates to just use
> physical address 0. That's a mask revision.
Sure, it's a mask rev for existing silicon, but the deployed fleet that
is impacted is in the many millions, and there are a very large number
of pieces impacted beyond just the OS community who need to prep.
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
next prev parent reply other threads:[~2018-05-24 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180523215715.89D9B610ED@crypto-ml.lab.linutronix.de>
2018-05-23 22:10 ` [MODERATED] Re: [PATCH v5 0/8] L1TFv4 5 Linus Torvalds
2018-05-23 22:19 ` Jiri Kosina
2018-05-23 22:28 ` Linus Torvalds
2018-05-24 14:12 ` Jon Masters [this message]
2018-05-23 22:24 ` Andrew Cooper
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=935c8f01-09b2-260f-78ac-32f62ab3b8de@redhat.com \
--to=jcm@redhat.com \
--cc=speck@linutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).