[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175190341018.3340086.4902525368986616519.git-patchwork-notify@kernel.org>
Date: Mon, 07 Jul 2025 15:50:10 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Luis Gerhorst <luis.gerhorst@....de>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
martin.lau@...ux.dev, eddyz87@...il.com, song@...nel.org,
yonghong.song@...ux.dev, john.fastabend@...il.com, kpsingh@...nel.org,
sdf@...ichev.me, haoluo@...gle.com, jolsa@...nel.org, mykolal@...com,
shuah@...nel.org, memxor@...il.com, yepeilin@...gle.com, skb99@...ux.ibm.com,
vmalik@...hat.com, isolodrai@...a.com, dxu@...uu.xyz, bpf@...r.kernel.org,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
paul.chaignon@...il.com
Subject: Re: [PATCH bpf-next v3 0/2] bpf: Fix and test aux usage after
do_check_insn()
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Sat, 5 Jul 2025 21:09:06 +0200 you wrote:
> Fix cur_aux()->nospec_result test after do_check_insn() referring to the
> to-be-analyzed (potentially unsafe) instruction, not the
> already-analyzed (safe) instruction. This might allow a unsafe insn to
> slip through on a speculative path. Create some tests from the
> reproducer [1].
>
> Commit d6f1c85f2253 ("bpf: Fall back to nospec for Spectre v1") should
> not be in any stable kernel yet, therefore bpf-next should suffice.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpf: Fix aux usage after do_check_insn()
https://git.kernel.org/bpf/bpf-next/c/dadb59104c64
- [bpf-next,v3,2/2] selftests/bpf: Add Spectre v4 tests
https://git.kernel.org/bpf/bpf-next/c/92974cef83b5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists