From: Jiri Kosina <jkosina@suse.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: spectrev1+
Date: Thu, 31 May 2018 16:39:29 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.1805311632300.27054@cbobk.fhfr.pm> (raw)
In-Reply-To: <alpine.LFD.2.21.999.1805310915210.29947@xps13.linux-foundation.org>
On Thu, 31 May 2018, speck for Linus Torvalds wrote:
> So for us _only_ on the speck mailing list, without any external
> encrypted document channels, can people fill us in?
>
> From the name, I'm assuming it's a bounds-checked store rather than a
> load that brings in a cache line in order to complete, but otherwise the
> exact same thing. No?
In principle yes, at least to my understanding.
Finding/creating a gadget that does speculative store followed by
corresponding/depending speculative load (that'd have been caught as
out-of-bound access in normal in-line execution) creates the sidechannel.
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2018-05-31 14:39 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 12:50 [MODERATED] spectrev1+ Jiri Kosina
2018-05-31 13:57 ` [MODERATED] spectrev1+ Josh Poimboeuf
2018-06-01 11:14 ` Peter Zijlstra
2018-06-01 12:46 ` Josh Poimboeuf
2018-05-31 14:11 ` David Woodhouse
2018-05-31 14:18 ` Linus Torvalds
2018-05-31 14:39 ` Jiri Kosina [this message]
2018-05-31 14:46 ` Peter Zijlstra
2018-05-31 14:55 ` Jiri Kosina
2018-05-31 18:49 ` Josh Poimboeuf
2018-05-31 18:55 ` Jiri Kosina
2018-05-31 20:36 ` Josh Poimboeuf
2018-05-31 20:52 ` Jiri Kosina
2018-05-31 21:28 ` Jiri Kosina
2018-05-31 21:51 ` Josh Poimboeuf
2018-05-31 21:59 ` Jiri Kosina
2018-05-31 23:09 ` Jon Masters
2018-05-31 20:54 ` Linus Torvalds
2018-06-01 11:03 ` Peter Zijlstra
2018-06-01 16:28 ` Jon Masters
2018-05-31 14:58 ` Peter Zijlstra
2018-05-31 18:41 ` Jon Masters
2018-05-31 21:02 ` Peter Zijlstra
2018-05-31 21:39 ` Josh Poimboeuf
2018-06-01 17:12 ` Konrad Rzeszutek Wilk
2018-06-01 21:29 ` Konrad Rzeszutek Wilk
2018-06-04 15:38 ` Peter Zijlstra
2018-06-04 15:44 ` Jiri Kosina
2018-06-04 16:23 ` Greg KH
2018-06-05 17:58 ` Josh Poimboeuf
2018-06-05 21:58 ` Jiri Kosina
2018-06-05 22:14 ` Linus Torvalds
2018-06-05 22:23 ` Jiri Kosina
2018-06-05 22:48 ` Linus Torvalds
2018-06-05 23:56 ` Jiri Kosina
2018-06-06 8:06 ` Norbert Manthey
2018-06-06 9:50 ` [MODERATED] spectrev1+ Norbert Manthey
2018-06-06 10:48 ` [MODERATED] spectrev1+ Greg KH
2018-06-06 16:14 ` [MODERATED] Is: smack, Was:Re: spectrev1+ Konrad Rzeszutek Wilk
2018-06-06 16:24 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-06-06 18:30 ` [MODERATED] " Norbert Manthey
2018-06-06 19:09 ` Thomas Gleixner
2018-06-07 11:38 ` [MODERATED] " Norbert Manthey
2018-06-07 12:31 ` Peter Zijlstra
2018-06-07 15:45 ` Konrad Rzeszutek Wilk
2018-06-07 16:10 ` Thomas Gleixner
2018-06-07 16:41 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-06-07 16:58 ` Josh Poimboeuf
2018-06-07 17:39 ` Norbert Manthey
2018-06-08 8:33 ` Martin Pohlack
2018-06-08 8:38 ` David Woodhouse
2018-06-09 12:31 ` Thomas Gleixner
2018-06-07 20:13 ` Is: smack, Was:Re: spectrev1+c Thomas Gleixner
2018-06-08 18:39 ` [MODERATED] Re: Is: smack, Was:Re: spectrev1+ Dave Hansen
2018-06-08 8:51 ` Jiri Kosina
2018-06-09 12:28 ` Thomas Gleixner
2018-06-08 18:15 ` [MODERATED] " Josh Poimboeuf
2018-06-08 18:19 ` Andrew Cooper
2018-06-08 19:04 ` Josh Poimboeuf
2018-06-09 12:35 ` Thomas Gleixner
2018-06-07 18:00 ` [MODERATED] spectrev1+ Jiri Kosina
2018-06-07 18:02 ` Andrew Cooper
2018-06-12 17:00 ` Jon Masters
2018-06-04 16:36 ` Josh Poimboeuf
2018-06-04 16:55 ` Peter Zijlstra
2018-06-04 17:02 ` Andrew Cooper
2018-06-04 18:53 ` Jiri Kosina
2018-06-04 19:07 ` Peter Zijlstra
2018-06-04 19:20 ` Jiri Kosina
2018-06-04 20:33 ` Jiri Kosina
2018-06-05 8:19 ` Peter Zijlstra
2018-06-04 17:14 ` Josh Poimboeuf
2018-06-04 17:18 ` Dave Hansen
2018-06-04 17:36 ` Josh Poimboeuf
2018-06-04 19:10 ` Peter Zijlstra
2018-06-04 19:51 ` Josh Poimboeuf
2018-06-05 1:09 ` Jon Masters
2018-06-05 1:15 ` Jon Masters
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=nycvar.YFH.7.76.1805311632300.27054@cbobk.fhfr.pm \
--to=jkosina@suse.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).