Hello:
This series was applied to bpf/bpf-next.git (master)
by Eduard Zingerman <[email protected]>:
On Tue, 11 Aug 2026 15:15:55 +0200 you wrote:
> check_atomic_rmw() open codes the mapping from a BPF_ATOMIC to the register
> it reads the old value into, the BPF_STX case of insn_def_regno() open codes
> the very same mapping a second time, the const folding and the liveness
> transfer functions a third and a fourth time, and BPF JITs need it as well
> to know which register a faulting BPF_PROBE_ATOMIC has to clear.
>
> Add a small helper so that all of them can share it. No functional change.
> The BPF_LOAD_ACQ case is there for the JITs, which do walk all instruction
> classes. const_reg_xfer() loses its explicit BPF_ATOMIC mode test since the
> helper checks class and mode itself; the BPF_PROBE_ATOMIC it additionally
> accepts cannot be seen there as it is only set from bpf_do_misc_fixups(),
> that is, after const folding has run. arg_track_xfer() keeps its mode test
> since that also guards the stack clearing next to it.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/6] bpf: Derive the atomic load register in one place
https://git.kernel.org/bpf/bpf-next/c/41c5dbb4be3c
- [bpf-next,v3,2/6] bpf, riscv: Clear fetch destination on faulting arena atomic
https://git.kernel.org/bpf/bpf-next/c/1519f488e8ce
- [bpf-next,v3,3/6] bpf, x86: Clear fetch destination on faulting arena atomic
https://git.kernel.org/bpf/bpf-next/c/cf92a108601a
- [bpf-next,v3,4/6] bpf, arm64: Clear fetch destination on faulting arena atomic
https://git.kernel.org/bpf/bpf-next/c/ea3f20cb5918
- [bpf-next,v3,5/6] bpf, s390: Clear fetch destination on faulting arena atomic
https://git.kernel.org/bpf/bpf-next/c/cc3e12330599
- [bpf-next,v3,6/6] selftests/bpf: Add arena fault tests for atomics with fetch
https://git.kernel.org/bpf/bpf-next/c/611a9f0d3dca
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.