public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: cip-dev@lists.cip-project.org, jan.kiszka@siemens.com,
	masami.ichikawa@miraclelinux.com
Subject: Fun ahead -- speculation problems being patched in 5.10.105
Date: Wed, 9 Mar 2022 22:37:16 +0100	[thread overview]
Message-ID: <20220309213716.GA9983@duo.ucw.cz> (raw)

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

Hi!

It looks like 5.10.105 will be "fun" release. There's big series of
arm64 related speculation tweaks, including

 |61f85b56f 558c30 o: 5.10| arm64: Mitigate spectre style branch history side channels

And apparently there are some problems on x86-64 side, too:

 |d185aa3cb e9b601 .: 5.10| x86/speculation: Update link to AMD speculation whitepaper
 |edc29f23a eafd98 o: 5.10| x86/speculation: Warn about Spectre v2 LFENCE mitigation
 |67997c824 0de05d o: 5.10| x86/speculation: Warn about eIBRS + LFENCE + Unprivileged eBPF + SMT

We have seen worse stuff for a hardware bug mitigation before. Scary
thing here is that arm64 patches are queued against 5.10 but not 4.19
or earlier.

Let me reiterate again that using complex out-of-order CPU is a bad
idea if you care about security.

Let me reiterate that JITs such as eBPF are complex/dangerous and
especially unpriviledged eBPF is risky.

v |316f1dd5e 44a391 o: 5.10| x86/speculation: Include unprivileged eBPF status in Spectre v2 mitigation reporting

Best regards,
                                                                Pavel

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

             reply	other threads:[~2022-03-09 21:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 21:37 Pavel Machek [this message]
2022-03-10  1:54 ` Fun ahead -- speculation problems being patched in 5.10.105 Masami Ichikawa

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=20220309213716.GA9983@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@siemens.com \
    --cc=masami.ichikawa@miraclelinux.com \
    /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