From: Jonathan Morton <chromatix99@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Dave Taht <dave.taht@gmail.com>,
Mikael Abrahamsson <swmike@swm.pp.se>,
Cake List <cake@lists.bufferbloat.net>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cake] [Cerowrt-devel] apu2 sqm/htb issue + a minor win for speeding up fq_codel itself
Date: Wed, 3 Oct 2018 21:32:23 +0300 [thread overview]
Message-ID: <7DF1B2AE-37DD-4C08-A3A0-2890FAD0CE27@gmail.com> (raw)
In-Reply-To: <87va6j9b97.fsf@toke.dk>
> On 3 Oct, 2018, at 8:43 pm, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> I don't suppose 18.06 enables any of the SPECTRE mitigations (was that
> an issue on ARM)?
That depends on the ARM core involved. Most of them in CPE devices (eg. Cortex-A5/7/53) have in-order execution engines, so should be immune - but it's not inconceivable that some of the mitigations are enabled regardless.
The WRT1200AC uses the Marvell 88F6820 which has a pair of Cortex-A9 cores. These are mildly out-of-order engines which would be at least theoretically vulnerable to Spectre v1, but that is not a kernel-level exploit. According to https://www.techarp.com/guides/complete-meltdown-spectre-cpu-list/4/#arm the Cortex-A9 is also vulnerable to Spectre v2 which is the branch-predictor poisoning attack, for which kernel-level mitigations may be appropriate. It is however immune to Meltdown.
I'm not familiar with precisely what mitigations are now in use on ARM. I am however certain that, on a device running only trustworthy code (ie. not running a Web browser), mitigating Spectre is unnecessary. If an attacker gets into a position to exploit it, he's already compromised the device enough to run a botnet anyway.
- Jonathan Morton
next prev parent reply other threads:[~2018-10-03 18:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 19:59 [Cake] " Dave Taht
2018-09-04 21:14 ` Dave Taht
2018-09-04 21:16 ` Dave Taht
2018-09-06 17:51 ` Pete Heist
2018-09-06 18:03 ` Dave Taht
2018-10-03 13:56 ` [Cake] [Cerowrt-devel] " Mikael Abrahamsson
2018-10-03 14:44 ` Dave Taht
2018-10-03 14:45 ` Dave Taht
2018-10-03 15:30 ` Mikael Abrahamsson
2018-10-03 16:05 ` Dave Taht
2018-10-03 17:43 ` Toke Høiland-Jørgensen
2018-10-03 17:53 ` Dave Taht
2018-10-03 18:32 ` Jonathan Morton [this message]
2018-10-03 20:12 ` Toke Høiland-Jørgensen
2018-10-05 12:52 ` Mikael Abrahamsson
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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7DF1B2AE-37DD-4C08-A3A0-2890FAD0CE27@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=swmike@swm.pp.se \
--cc=toke@toke.dk \
/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