bpf: Mark existing lock-safe kfuncs with KF_SPINLOCK_SAFE

Browse source

The verifier currently keeps a hard-coded list of kfuncs that may be
called while holding a bpf_spin_lock. With KF_SPINLOCK_SAFE available,
retaining this list creates two sources of truth and requires verifier
changes whenever another lock-safe kfunc is added.

Mark every kfunc currently accepted by kfunc_spin_allowed() with
KF_SPINLOCK_SAFE. This covers the graph, numeric iterator, resource
spin lock, arena, and stream kfuncs.

Remove the obsolete category checks and make kfunc_spin_allowed() rely
solely on the kfunc registration metadata. This preserves the behavior
of existing kfuncs while using the same mechanism for built-in and
module kfuncs.

Signed-off-by: Kaitao Cheng <chengkaitao@kylinos.cn>
Acked-by: Leon Hwang <leon.hwang@linux.dev>
Link: https://lore.kernel.org/bpf/20260805153340.34776-3-kaitao.cheng@linux.dev
Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>

...

This commit is contained in:

Kaitao Cheng 2026-08-05 23:33:39 +08:00 • committed by Kumar Kartikeya Dwivedi

parent ed3b3093b6

commit 7619a0ee93

No known key found for this signature in database

GPG key ID: 472D377B63542F83

4 changed files with 36 additions and 66 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

6

kernel/bpf/arena.c

View file

56

kernel/bpf/helpers.c

View file

8

kernel/bpf/rqspinlock.c

View file

32

kernel/bpf/verifier.c

View file