From: Mark Rutland <mark.rutland@arm.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
dan.j.williams@intel.com, elena.reshetova@intel.com,
corbet@lwn.net, alan@linux.intel.com, peterz@infradead.org,
will.deacon@arm.com, gregkh@linuxfoundation.org,
tglx@linutronix.de, Paul Turner <pjt@google.com>
Subject: Re: [RFCv2 2/4] Documentation: document nospec helpers
Date: Sun, 7 Jan 2018 13:06:11 +0000 [thread overview]
Message-ID: <20180107130610.3vllt5cm2b3orukd@salmiak> (raw)
In-Reply-To: <f7a88365-8936-0d5e-0764-8664429e6305@infradead.org>
On Sat, Jan 06, 2018 at 09:20:59PM -0800, Randy Dunlap wrote:
> On 01/05/18 06:57, Mark Rutland wrote:
> > Document the rationale and usage of the new nospec*() helpers.
> >
> > Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> > Signed-off-by: Will Deacon <will.deacon@arm.com>
> > Cc: Dan Williams <dan.j.williams@intel.com>
> > Cc: Jonathan Corbet <corbet@lwn.net>
> > Cc: Peter Zijlstra <peterz@infradead.org>
> > ---
> > Documentation/speculation.txt | 166 ++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 166 insertions(+)
> > create mode 100644 Documentation/speculation.txt
> >
> > diff --git a/Documentation/speculation.txt b/Documentation/speculation.txt
> > new file mode 100644
> > index 000000000000..748fcd4dcda4
> > --- /dev/null
> > +++ b/Documentation/speculation.txt
> > @@ -0,0 +1,166 @@
> > +
> > +Typically speculative execution cannot be observed from architectural state,
> > +such as the contents of registers. However, in some cases it is possible to
> > +observe its impact on microarchitectural state, such as the presence or
> > +absence of data in caches. Such state may form side-channels which can be
> > +observed to extract secret information.
>
> I'm curious about what it takes to observe this...
>
> or is that covered in the exploit papers?
That's covered elsewhere, e.g.
https://googleprojectzero.blogspot.co.uk/2018/01/reading-privileged-memory-with-side.html
I'll add some references.
Thanks,
Mark.
next prev parent reply other threads:[~2018-01-07 13:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 14:57 [RFCv2 0/4] API for inhibiting speculative arbitrary read primitives Mark Rutland
2018-01-05 14:57 ` Mark Rutland
2018-01-05 14:57 ` [RFCv2 1/4] asm-generic/barrier: add generic nospec helpers Mark Rutland
2018-01-05 14:57 ` Mark Rutland
2018-01-08 21:47 ` Mark Salter
2018-01-05 14:57 ` [RFCv2 2/4] Documentation: document " Mark Rutland
2018-01-05 14:57 ` Mark Rutland
2018-01-07 5:20 ` Randy Dunlap
2018-01-07 13:06 ` Mark Rutland [this message]
2018-01-07 10:27 ` Geert Uytterhoeven
2018-01-07 10:27 ` Geert Uytterhoeven
2018-01-05 14:57 ` [RFCv2 3/4] arm64: implement nospec_ptr() Mark Rutland
2018-01-05 14:57 ` [RFCv2 4/4] bpf: inhibit speculated out-of-bounds pointers Mark Rutland
2018-01-05 14:57 ` Mark Rutland
2018-01-05 16:38 ` Dan Williams
2018-01-05 16:48 ` Mark Rutland
2018-01-05 17:04 ` Alexei Starovoitov
2018-01-08 12:59 ` Reshetova, Elena
2018-01-08 12:59 ` Reshetova, Elena
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=20180107130610.3vllt5cm2b3orukd@salmiak \
--to=mark.rutland@arm.com \
--cc=alan@linux.intel.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=elena.reshetova@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
/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).