From: Peter Zijlstra <peterz@infradead.org>
To: speck@linutronix.de
Subject: [MODERATED] Re: [patch V3 5/9] MDS basics 5
Date: Fri, 22 Feb 2019 10:20:21 +0100 [thread overview]
Message-ID: <20190222092021.GW32494@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <7e028ea7-dcc7-e931-a888-df60f69a348c@citrix.com>
On Fri, Feb 22, 2019 at 12:46:46AM +0000, speck for Andrew Cooper wrote:
> On 21/02/2019 23:44, speck for Thomas Gleixner wrote:
> > + There is one non maskable exception which returns through paranoid exit
> > + and is not mitigated: #DF. If user space is able to trigger a double
> > + fault the possible MDS leakage is the least problem to worry about.
>
> What about espfix64? An IRET fault from that ends up at #DF, and
> purposefully recovers. It is trigger-able from at least modify_ldt().
>
> The #DF path is normally fatal, but in the cases that it's not, an extra
> VERW isn't going to be the slow part.
What about the #MC, do_mce has paranoid=1 on.
next prev parent reply other threads:[~2019-02-22 9:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 23:44 [patch V3 0/9] MDS basics 0 Thomas Gleixner
2019-02-21 23:44 ` [patch V3 1/9] MDS basics 1 Thomas Gleixner
2019-02-22 6:53 ` [MODERATED] " Greg KH
2019-02-22 7:30 ` Borislav Petkov
2019-02-21 23:44 ` [patch V3 2/9] MDS basics 2 Thomas Gleixner
2019-02-21 23:44 ` [patch V3 3/9] MDS basics 3 Thomas Gleixner
2019-02-21 23:44 ` [patch V3 4/9] MDS basics 4 Thomas Gleixner
2019-02-22 6:58 ` [MODERATED] " Greg KH
2019-02-22 10:44 ` Thomas Gleixner
2019-02-22 14:36 ` [MODERATED] " Greg KH
2019-02-22 22:38 ` Thomas Gleixner
2019-02-22 7:45 ` [MODERATED] Encrypted Message Jon Masters
2019-02-22 17:16 ` [MODERATED] " Linus Torvalds
2019-02-22 17:40 ` Thomas Gleixner
2019-02-22 7:50 ` [MODERATED] Re: [patch V3 4/9] MDS basics 4 Borislav Petkov
2019-02-21 23:44 ` [patch V3 5/9] MDS basics 5 Thomas Gleixner
2019-02-22 0:46 ` [MODERATED] " Andrew Cooper
2019-02-22 7:00 ` Thomas Gleixner
2019-02-22 9:20 ` Peter Zijlstra [this message]
2019-02-22 10:23 ` Thomas Gleixner
2019-02-21 23:44 ` [patch V3 6/9] MDS basics 6 Thomas Gleixner
2019-02-21 23:44 ` [patch V3 7/9] MDS basics 7 Thomas Gleixner
2019-02-22 7:08 ` [MODERATED] " Greg KH
2019-02-21 23:44 ` [patch V3 8/9] MDS basics 8 Thomas Gleixner
2019-02-22 7:14 ` [MODERATED] " Greg KH
2019-02-22 8:55 ` Borislav Petkov
2019-02-21 23:44 ` [patch V3 9/9] MDS basics 9 Thomas Gleixner
2019-02-22 7:50 ` [MODERATED] " Greg KH
2019-02-22 10:38 ` Thomas Gleixner
2019-02-22 14:44 ` [MODERATED] " Greg KH
2019-02-22 15:53 ` [MODERATED] " Borislav Petkov
2019-02-22 15:54 ` [MODERATED] " Borislav Petkov
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=20190222092021.GW32494@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.