From: Russell King <rmk@armlinux.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot, cache speculation side channel attacks and ARM
Date: Sat, 20 Jan 2018 12:29:22 +0000 [thread overview]
Message-ID: <20180120122922.GA22862@flint.armlinux.org.uk> (raw)
In-Reply-To: <20180120113119.6c957ccc@why.wild-wind.fr.eu.org>
On Sat, Jan 20, 2018 at 11:31:19AM +0000, Marc Zyngier wrote:
> Define enough. These patches allow these CPUs to cope with variant-2,
> and only variant-2. Variant-1 is still work in progress across all
> architectures, variant-3 (aka Meltdown) doesn't concern 32bit ARM
> implementations, and only A15 is susceptible to variant-3a.
I think you need to be really careful about statements like this.
As you know, it is possible to run a 32bit environment in a VM on
the 64bit CPUs. So, its entirely possible to run a 32bit setup
on a Cortex A72 for example, and that means such a setup _is_
vulnerable to variant 3a.
Do people do this? That isn't something we can really know, but
I think as long as its allowed, you can bet that someone will,
and someone will end up using it in a production environment.
So, it can't be ignored.
--
Russell King
next prev parent reply other threads:[~2018-01-20 12:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 21:56 [U-Boot] U-Boot, cache speculation side channel attacks and ARM Tom Rini
2018-01-19 22:21 ` Mark Kettenis
2018-01-19 23:10 ` Nishanth Menon
2018-01-20 9:47 ` Michael Nazzareno Trimarchi
2018-01-20 10:45 ` Marc Zyngier
2018-01-20 10:51 ` Marc Zyngier
2018-01-20 10:42 ` Marc Zyngier
2018-01-20 10:45 ` Michael Nazzareno Trimarchi
2018-01-20 11:31 ` Marc Zyngier
2018-01-20 12:13 ` Michael Nazzareno Trimarchi
2018-01-20 12:29 ` Russell King [this message]
2018-01-20 12:45 ` Marc Zyngier
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=20180120122922.GA22862@flint.armlinux.org.uk \
--to=rmk@armlinux.org.uk \
--cc=u-boot@lists.denx.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