Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Ryan Roberts <ryan.roberts@arm.com>,
	Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	John Fastabend <john.fastabend@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v1] arm64: Mitigate Spectre v1 in the BPF interpreter
Date: Fri, 20 Nov 2026 10:02:52 +0000	[thread overview]
Message-ID: <awAay4FFj1_wQtaL@arm.com> (raw)
In-Reply-To: <DMYSI3BOQWOC.2P2FZB0H872DR@gmail.com>

On Thu, Nov 19, 2026 at 01:18:03AM +0000, Alexei Starovoitov wrote:
> On Tue, Nov 17, 2026 at 09:23 AM Ryan Roberts <ryan.roberts@arm.com> wrote:
> > The arm64 JIT implements BPF_NOSPEC with a speculation barrier, but the
> > interpreter calls barrier_nospec(), which falls back to a no-op on
> > arm64. Programs executed by the interpreter therefore lack the
> > Spectre-v1 barriers assumed by the verifier. Contrary to the code
> > comment, kernel-wide SSBD does not provide this protection, since it
> > mitigates Spectre v4 rather than Spectre v1.
> 
> Nack.
> In bpf-next arm64 has no interpreter when the JIT is built.

And what about current mainline/stable or when one disables BPF_JIT
explicitly? Should we force BPF_JIT=y as well when ALWAYS_ON=y?

-- 
Catalin

      reply	other threads:[~2026-11-20 10:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 17:23 [PATCH v1] arm64: Mitigate Spectre v1 in the BPF interpreter Ryan Roberts
2026-11-18 14:27 ` Luis Gerhorst
2026-11-19  1:18 ` Alexei Starovoitov
2026-11-20 10:02   ` Catalin Marinas [this message]

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=awAay4FFj1_wQtaL@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=ryan.roberts@arm.com \
    --cc=stable@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=will@kernel.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
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