From: Eduard Zingerman <eddyz87@gmail.com>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Emil Tsalapatis <emil@etsalapatis.com>,
kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v1 2/2] bpf: Fix is_tracing_prog_type() to cover fentry/fexit/fmod_ret
Date: Tue, 21 Jul 2026 11:26:49 -0700 [thread overview]
Message-ID: <e7312dd40b06f19429f157aa100914c8d5536232.camel@gmail.com> (raw)
In-Reply-To: <20260719113551.1294284-3-memxor@gmail.com>
On Sun, 2026-07-19 at 13:35 +0200, Kumar Kartikeya Dwivedi wrote:
...
> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> index bb6e16668d0d..3fe2410c7ce3 100644
> --- a/kernel/bpf/verifier.c
> +++ b/kernel/bpf/verifier.c
...
> @@ -12317,6 +12323,10 @@ static int check_kfunc_args(struct bpf_verifier_env *env, struct bpf_call_arg_me
> verbose(env, "allocated object must be referenced\n");
> return -EINVAL;
> }
> + if (is_tracing_prog_type(env->prog)) {
> + verbose(env, "tracing progs cannot use bpf_{list_head,rb_root} yet\n");
> + return -EINVAL;
> + }
I think this and the next checks should be moved to
__process_kf_arg_ptr_to_graph_root() or check_reg_allocation_locked().
Could you please elaborate a bit on why is it necessary at all?
> ret = process_kf_arg_ptr_to_list_head(env, reg, argno, meta);
> if (ret < 0)
> return ret;
> @@ -12333,6 +12343,10 @@ static int check_kfunc_args(struct bpf_verifier_env *env, struct bpf_call_arg_me
> verbose(env, "allocated object must be referenced\n");
> return -EINVAL;
> }
> + if (is_tracing_prog_type(env->prog)) {
> + verbose(env, "tracing progs cannot use bpf_{list_head,rb_root} yet\n");
> + return -EINVAL;
> + }
> ret = process_kf_arg_ptr_to_rbtree_root(env, reg, argno, meta);
> if (ret < 0)
> return ret;
...
prev parent reply other threads:[~2026-07-21 18:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 11:35 [PATCH bpf-next v1 0/2] Open up res_spin_lock for tracing programs, fix is_tracing_prog_type() Kumar Kartikeya Dwivedi
2026-07-19 11:35 ` [PATCH bpf-next v1 1/2] bpf: Allow bpf_res_spin_lock() in all contexts Kumar Kartikeya Dwivedi
2026-07-19 11:56 ` sashiko-bot
2026-07-19 12:02 ` Kumar Kartikeya Dwivedi
2026-07-20 22:00 ` Emil Tsalapatis
2026-07-21 17:53 ` Eduard Zingerman
2026-07-19 11:35 ` [PATCH bpf-next v1 2/2] bpf: Fix is_tracing_prog_type() to cover fentry/fexit/fmod_ret Kumar Kartikeya Dwivedi
2026-07-19 14:09 ` sashiko-bot
2026-07-19 14:12 ` Kumar Kartikeya Dwivedi
2026-07-20 22:40 ` Emil Tsalapatis
2026-07-21 18:26 ` Eduard Zingerman [this message]
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=e7312dd40b06f19429f157aa100914c8d5536232.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=emil@etsalapatis.com \
--cc=kernel-team@meta.com \
--cc=kkd@meta.com \
--cc=memxor@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox