Re: [PATCH bpf-next v6 0/3] bpf: Fix arena memory incoherence

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Mon, 19 Oct 2026 20:11:05 +0000 you wrote:
> Arena memory is tracked in two places: the range tree, which records
> which addresses are allocated, and the kernel and user page tables. The
> two are updated under different locks, and that leaves two races:
> 
> - Since b8467290edab ("bpf: arena: make arena kfuncs any context safe"),
>   a free releases its range before the kernel TLB flush and the user zap
>   complete. A concurrent allocation can then write through stale
>   translations into pages that are about to be freed.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v6,1/3] bpf: Revalidate faulted arena pages before installing user mappings
    https://git.kernel.org/bpf/bpf-next/c/05bee0638bac
  - [bpf-next,v6,2/3] bpf: Fix arena race between page free and alloc leading to incoherency
    https://git.kernel.org/bpf/bpf-next/c/7244a2e58d21
  - [bpf-next,v6,3/3] selftests/bpf: Add arena allocation race tests
    https://git.kernel.org/bpf/bpf-next/c/6c372031078c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html