From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jonathan Morton <chromatix99@gmail.com>
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: [Cerowrt-devel] [Cake] apu2 sqm/htb issue + a minor win for speeding up fq_codel itself
Date: Wed, 03 Oct 2018 22:12:50 +0200 [thread overview]
Message-ID: <87sh1maiwt.fsf@toke.dk> (raw)
In-Reply-To: <7DF1B2AE-37DD-4C08-A3A0-2890FAD0CE27@gmail.com>
Jonathan Morton <chromatix99@gmail.com> writes:
> 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.
Yup, especially on openwrt, where most daemons run as root anyway :)
I would assume that something like the retpoline indirect function call
protection is not actually enabled on openwrt; but since we were talking
about performance regressions, that is certainly a major one...
-Toke
next prev parent reply other threads:[~2018-10-03 20:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 19:59 [Cerowrt-devel] " Dave Taht
2018-09-04 21:14 ` Dave Taht
2018-09-04 21:16 ` Dave Taht
2018-09-06 17:51 ` [Cerowrt-devel] [Cake] " Pete Heist
2018-09-06 18:03 ` Dave Taht
2018-10-03 13:56 ` 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
2018-10-03 20:12 ` Toke Høiland-Jørgensen [this message]
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sh1maiwt.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.taht@gmail.com \
--cc=swmike@swm.pp.se \
/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