From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 209] spectre-proof speculative execution
Date: Mon, 18 May 2020 19:06:41 +0000
Message-ID: <bug-209-13-NYIVNeppec@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-209-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=209
Yehowshua <yimmanuel3@gatech.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yimmanuel3@gatech.edu
--- Comment #3 from Yehowshua <yimmanuel3@gatech.edu> ---
According to the Spectre paper here: https://spectreattack.com/spectre.pdf
there are multiple Spectre style vulnerabilities. I will focus here on Spectre
variant 1 from the paper.
The solution I present below comes from the Solutions section of the paper in
"Mitigation Options".
Variant 1 of the attack can be prevented by having commit buffers from L2 or
memory to L1 during speculative execution, and by having a commit buffer from
reg to L1.
Its all about making sure that cache is reverted during L1 so that you can
cache flushes cannot leak sensitive information.
Oh, and cache flushes should be disallowed during speculative execution.
The timing concept you describe
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next parent reply index
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-209-13@https.bugs.libre-soc.org/>
2020-05-18 19:06 ` bugzilla-daemon [this message]
2020-05-18 19:24 ` bugzilla-daemon
2020-05-18 19:25 ` Yehowshua
2020-05-18 19:38 ` Luke Kenneth Casson Leighton
2020-05-18 19:59 ` bugzilla-daemon
2020-05-18 20:51 ` bugzilla-daemon
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=bug-209-13-NYIVNeppec@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git