From: Jon Masters <jcm@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: spectrev1+
Date: Tue, 12 Jun 2018 13:00:34 -0400 [thread overview]
Message-ID: <b4f8103d-6c54-cf84-408b-0708a46d518e@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.21.999.1806051511320.13286@i7.lan>
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
On 06/05/2018 06:14 PM, speck for Linus Torvalds wrote:
>
>
> On Tue, 5 Jun 2018, speck for Jiri Kosina wrote:
>>
>> speculative return address overwrite
>
> I don't believe in this one to begin with.
>
> The return address is always taken from the RSB.
For one thing, it's known that Intel has several different RSBs in their
designs - an architectural RSB and a speculative RSB (SRSB), plus they
will search the BTB at least on underflow. In the SRSB case, whenever
they detect a CALL during instruction decode, they'll stash the return
in the SRSB even if it's never executed. So you could minimally cause an
SRSB entry to be created that never matched with a call.
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
next prev parent reply other threads:[~2018-06-12 17:00 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
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 [this message]
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=b4f8103d-6c54-cf84-408b-0708a46d518e@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).