Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <[email protected]>:

On Sat, 14 Feb 2026 20:40:37 +0800 you wrote:
> From: Kaitao Cheng <[email protected]>
> 
> When using bpf_kptr_xchg, we triggered the following error:
>     31: (85) call bpf_kptr_xchg#194
>     function calls are not allowed while holding a lock
> bpf_kptr_xchg can now be used in lock-held contexts, so we extended
> its usage scope in [patch 1/5].
> 
> [...]

Here is the summary with links:
  - [RESEND,v7,1/5] bpf: allow calling bpf_kptr_xchg while holding a lock
    https://git.kernel.org/bpf/bpf-next/c/964c0747686a
  - [RESEND,v7,2/5] bpf: allow using bpf_kptr_xchg even if the NON_OWN_REF flag 
is set
    https://git.kernel.org/bpf/bpf-next/c/ee9886c40aae
  - [RESEND,v7,3/5] selftests/bpf: Add supplementary tests for bpf_kptr_xchg
    https://git.kernel.org/bpf/bpf-next/c/580fa3430b5d
  - [RESEND,v7,4/5] bpf: allow using bpf_kptr_xchg even if the MEM_RCU flag is 
set
    https://git.kernel.org/bpf/bpf-next/c/fb1590448ff7
  - [RESEND,v7,5/5] selftests/bpf: Add test case for rbtree nodes that contain 
both bpf_refcount and kptr fields.
    https://git.kernel.org/bpf/bpf-next/c/ed8fa4b8894f

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



Reply via email to