From: patchwork-bot+netdevbpf@kernel.org
To: Luis Gerhorst <luis.gerhorst@fau.de>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org,
shuah@kernel.org, isolodrai@meta.com, memxor@gmail.com,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/2] bpf: Fix verifier_bug_if to account for BPF_CALL
Date: Thu, 29 Jan 2026 02:50:08 +0000 [thread overview]
Message-ID: <176965500835.2326292.18318567298833649268.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260127115912.3026761-1-luis.gerhorst@fau.de>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 27 Jan 2026 12:59:10 +0100 you wrote:
> This fixes the verifier_bug_if() that runs on nospec_result to not trigger
> for BPF_CALL (bug reported by Hu, Mei, and Mu). See patch 1 for a full
> description and patch 2 for a test (based on the PoC from the report).
>
> While working on this I noticed two other problems:
>
> - nospec_result is currently ignored for BPF_CALL during patching, but it
> may be required if we assume the CPU may speculate into/out of functions.
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Fix verifier_bug_if to account for BPF_CALL
https://git.kernel.org/bpf/bpf-next/c/cd3b6a3d49f8
- [bpf-next,2/2] bpf: Test nospec after dead stack write in helper
https://git.kernel.org/bpf/bpf-next/c/60d2c438c1bb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-29 2:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 11:59 [PATCH bpf-next 0/2] bpf: Fix verifier_bug_if to account for BPF_CALL Luis Gerhorst
2026-01-27 11:59 ` [PATCH bpf-next 1/2] " Luis Gerhorst
2026-01-27 11:59 ` [PATCH bpf-next 2/2] bpf: Test nospec after dead stack write in helper Luis Gerhorst
2026-01-27 12:37 ` [PATCH bpf-next 0/2] bpf: Fix verifier_bug_if to account for BPF_CALL Luis Gerhorst
2026-01-29 2:50 ` patchwork-bot+netdevbpf [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=176965500835.2326292.18318567298833649268.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=isolodrai@meta.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luis.gerhorst@fau.de \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.