From: "Kumar Kartikeya Dwivedi" <memxor@gmail.com>
To: "Kaitao Cheng" <kaitao.cheng@linux.dev>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Eduard Zingerman" <eddyz87@gmail.com>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
"Song Liu" <song@kernel.org>,
"Yonghong Song" <yonghong.song@linux.dev>,
"Jiri Olsa" <jolsa@kernel.org>,
"Emil Tsalapatis" <emil@etsalapatis.com>,
"John Fastabend" <john.fastabend@gmail.com>,
"Ihor Solodrai" <ihor.solodrai@linux.dev>
Cc: <bpf@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Kaitao Cheng" <chengkaitao@kylinos.cn>
Subject: Re: [PATCH] bpf: add KF_SPIN_LOCK flag for kfuncs under bpf_spin_lock
Date: Tue, 04 Aug 2026 10:43:28 +0200 [thread overview]
Message-ID: <DKG0YUDSTBUY.1X220287HT9V3@gmail.com> (raw)
In-Reply-To: <20260804083212.79271-1-kaitao.cheng@linux.dev>
On Tue Aug 4, 2026 at 10:32 AM CEST, Kaitao Cheng wrote:
> From: Kaitao Cheng <chengkaitao@kylinos.cn>
>
> Introduce the KF_SPIN_LOCK kfunc metadata flag in BTF so kfuncs may be
> explicitly marked as safe to call while holding bpf_spin_lock.
>
> Allow kfuncs defined in kernel modules to be marked with KF_SPIN_LOCK.
>
> Example: BTF_ID_FLAGS(func, $kfunc_name, KF_SPIN_LOCK)
>
> Signed-off-by: Kaitao Cheng <chengkaitao@kylinos.cn>
> ---
> include/linux/btf.h | 1 +
> kernel/bpf/verifier.c | 20 +++++++++++++++-----
> 2 files changed, 16 insertions(+), 5 deletions(-)
>
> diff --git a/include/linux/btf.h b/include/linux/btf.h
> index c09b7994de4e..380dc10b6750 100644
> --- a/include/linux/btf.h
> +++ b/include/linux/btf.h
> @@ -79,6 +79,7 @@
> #define KF_ARENA_ARG1 (1 << 14) /* kfunc takes an arena pointer as its first argument */
> #define KF_ARENA_ARG2 (1 << 15) /* kfunc takes an arena pointer as its second argument */
> #define KF_IMPLICIT_ARGS (1 << 16) /* kfunc has implicit arguments supplied by the verifier */
> +#define KF_SPIN_LOCK (1 << 17) /* kfunc is allowed inside bpf_spin_lock-ed region */
>
> /*
> * Tag marking a kernel function as a kfunc. This is meant to minimize the
> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> index 7aa47342dc65..9f3feba3c2fe 100644
> --- a/kernel/bpf/verifier.c
> +++ b/kernel/bpf/verifier.c
> @@ -11657,11 +11657,21 @@ static bool is_bpf_stream_kfunc(u32 btf_id)
> btf_id == special_kfunc_list[KF_bpf_stream_print_stack];
> }
>
> -static bool kfunc_spin_allowed(u32 btf_id)
> +static bool kfunc_spin_allowed(struct bpf_verifier_env *env, s32 func_id, s16 offset)
> {
> - return is_bpf_graph_api_kfunc(btf_id) || is_bpf_iter_num_api_kfunc(btf_id) ||
> - is_bpf_res_spin_lock_kfunc(btf_id) || is_bpf_arena_kfunc(btf_id) ||
> - is_bpf_stream_kfunc(btf_id);
> + struct bpf_kfunc_meta kfunc;
> + int err;
> +
> + if (is_bpf_graph_api_kfunc(func_id) || is_bpf_iter_num_api_kfunc(func_id) ||
> + is_bpf_res_spin_lock_kfunc(func_id) || is_bpf_arena_kfunc(func_id) ||
> + is_bpf_stream_kfunc(func_id))
> + return true;
> +
> + err = fetch_kfunc_meta(env, func_id, offset, &kfunc);
> + if (err || !kfunc.flags)
> + return false;
> +
> + return *kfunc.flags & KF_SPIN_LOCK;
> }
>
> static bool is_sync_callback_calling_kfunc(u32 btf_id)
> @@ -17289,7 +17299,7 @@ static int do_check_insn(struct bpf_verifier_env *env, bool *do_print_state)
> insn->imm != BPF_FUNC_spin_unlock &&
> insn->imm != BPF_FUNC_kptr_xchg) ||
> (insn->src_reg == BPF_PSEUDO_KFUNC_CALL &&
> - (insn->off != 0 || !kfunc_spin_allowed(insn->imm)))) {
> + !kfunc_spin_allowed(env, insn->imm, insn->off))) {
> verbose(env,
> "function calls are not allowed while holding a lock\n");
> return -EINVAL;
Why not apply it to all of the existing kfuncs? Also, use [PATCH bpf-next] subject.
pw-bot: cr
next prev parent reply other threads:[~2026-08-04 8:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 8:32 [PATCH] bpf: add KF_SPIN_LOCK flag for kfuncs under bpf_spin_lock Kaitao Cheng
2026-08-04 8:43 ` Kumar Kartikeya Dwivedi [this message]
2026-08-04 9:37 ` Kaitao Cheng
2026-08-04 9:42 ` Kumar Kartikeya Dwivedi
2026-08-04 10:09 ` Kaitao Cheng
2026-08-04 10:22 ` Kumar Kartikeya Dwivedi
2026-08-04 12:42 ` Leon Hwang
2026-08-04 13:05 ` Kumar Kartikeya Dwivedi
2026-08-04 9:15 ` Leon Hwang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DKG0YUDSTBUY.1X220287HT9V3@gmail.com \
--to=memxor@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chengkaitao@kylinos.cn \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kaitao.cheng@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.