From: Jon Masters <jcm@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: ARCH_CAPABILITIES note
Date: Wed, 6 Jun 2018 13:46:56 -0400 [thread overview]
Message-ID: <17190e68-050d-f7f1-be61-6282a9023a44@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.21.999.1806060833460.10911@i7.lan>
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
On 06/06/2018 11:50 AM, speck for Linus Torvalds wrote:
> Also, afaik, lfence doesn't necessarily wait for the store buffer to
> drain, but since it waits for all preceding stores to be stable, it at
> least guarantees that stores _are_ in the store buffer, and there are no
> speculative store buffer entries, so it avoids the store buffer bypass
> (and the SB poisoning that I haven't actually seen verified if Intel has
> problems with or not).
Since SSB is public now, I fished with friends at Graz to see what
they'd investigated there. They said they did a bunch of testing already
and are working on more attacks using speculative store buffer function
pointer indirection into kernel address space.
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
next prev parent reply other threads:[~2018-06-06 17:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 16:41 [MODERATED] ARCH_CAPABILITIES note Jon Masters
2018-06-05 18:27 ` [MODERATED] " Dave Hansen
2018-06-05 18:33 ` Linus Torvalds
2018-06-05 18:48 ` Jon Masters
2018-06-05 19:19 ` Thomas Gleixner
2018-06-05 19:27 ` [MODERATED] " Jon Masters
2018-06-05 19:36 ` Linus Torvalds
2018-06-06 15:20 ` Dave Hansen
2018-06-06 15:50 ` Linus Torvalds
2018-06-06 17:46 ` Jon Masters [this message]
2018-06-06 16:04 ` Linus Torvalds
2018-06-06 17:04 ` Dave Hansen
2018-06-05 18:45 ` David Woodhouse
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=17190e68-050d-f7f1-be61-6282a9023a44@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).