Re: [PATCH 0/2] bpf: Fix torn writes in non-prealloc htab with BPF_F_LOCK

[patchwork-bot+netdevbpf@kernel.org]

Hello:

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

On Wed, 01 Apr 2026 06:50:35 -0700 you wrote:
> A torn write issue was reported in htab_map_update_elem() with
> BPF_F_LOCK on hash maps. The BPF_F_LOCK fast path performs
> a lockless lookup and copies the value under the element's embedded
> spin_lock. A concurrent delete can free the element via
> bpf_mem_cache_free(), which allows immediate reuse. When
> alloc_htab_elem() recycles the same memory, it writes the value with
> plain copy_map_value() without taking the spin_lock, racing with the
> stale lock holder and producing torn writes.
> 
> [...]

Here is the summary with links:
  - [1/2] bpf: Use copy_map_value_locked() in alloc_htab_elem() for BPF_F_LOCK
    https://git.kernel.org/bpf/bpf-next/c/07738bc566c3
  - [2/2] selftests/bpf: Add torn write detection test for htab BPF_F_LOCK
    https://git.kernel.org/bpf/bpf-next/c/f64eb44ce906

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