Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <[email protected]>:
On Wed, 5 Aug 2026 23:33:37 +0800 you wrote:
> The verifier currently has a hard-coded allowlist of kfuncs that may be
> called while a BPF program holds a bpf_spin_lock. This works for the
> small set of built-in kfuncs known to the verifier, but it does not give
> kfunc providers a registration-time way to declare that a kfunc is safe
> in such a region. In particular, module kfuncs cannot be added to that
> allowlist without changing verifier code.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/3] bpf: Add KF_SPINLOCK_SAFE flag for kfuncs under
bpf_spin_lock
https://git.kernel.org/bpf/bpf-next/c/ed3b3093b624
- [bpf-next,v2,2/3] bpf: Mark existing lock-safe kfuncs with KF_SPINLOCK_SAFE
https://git.kernel.org/bpf/bpf-next/c/7619a0ee9340
- [bpf-next,v2,3/3] selftests/bpf: Test module kfunc calls under spin lock
https://git.kernel.org/bpf/bpf-next/c/bca83aa31f15
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
