From: Eduard Zingerman <eddyz87@gmail.com>
To: Yonghong Song <yonghong.song@linux.dev>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@fb.com
Subject: Re: [PATCH bpf-next 2/2] bpf: Report which member makes a kfunc return type unsupported
Date: Mon, 24 Aug 2026 12:27:11 -0700 [thread overview]
Message-ID: <5add32b3e212f7bcc01eb920c51749ae6d2aafcd.camel@gmail.com> (raw)
In-Reply-To: <20260824144948.992324-1-yonghong.song@linux.dev>
On Mon, 2026-08-24 at 07:49 -0700, Yonghong Song wrote:
...
> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> index 9aa29c367008..c6aecba6437a 100644
> --- a/kernel/bpf/verifier.c
> +++ b/kernel/bpf/verifier.c
> @@ -11623,10 +11623,14 @@ static bool is_kfunc_arg_implicit(const struct bpf_call_arg_meta *meta, u32 arg_
> return argn <= arg_idx;
> }
>
> -/* Returns true if struct is composed of scalars, 4 levels of nesting allowed */
> -bool btf_type_is_scalar_struct(struct bpf_verifier_env *env,
> - const struct btf *btf,
> - const struct btf_type *t, int rec)
> +/*
> + * Returns true if struct is composed of scalars, 4 levels of nesting allowed.
> + * On failure @bad, when given, names the member that made the answer no, so a
> + * diagnostic can point at it rather than at the whole type.
> + */
> +static bool btf_scalar_struct_walk(struct bpf_verifier_env *env, const struct btf *btf,
> + const struct btf_type *t, int rec,
> + const struct btf_member **bad)
> {
> const struct btf_type *member_type;
> const struct btf_member *member;
> @@ -11644,23 +11648,35 @@ bool btf_type_is_scalar_struct(struct bpf_verifier_env *env,
> verbose(env, "max struct nesting depth exceeded\n");
> return false;
> }
> - if (!btf_type_is_scalar_struct(env, btf, member_type, rec + 1))
> + if (!btf_scalar_struct_walk(env, btf, member_type, rec + 1, bad))
> return false;
> continue;
> }
> if (btf_type_is_array(member_type)) {
> array = btf_array(member_type);
> if (!array->nelems)
> - return false;
> + goto bad_member;
> member_type = btf_type_skip_modifiers(btf, array->type, NULL);
> if (!btf_type_is_scalar(member_type))
> - return false;
> + goto bad_member;
> continue;
> }
> if (!btf_type_is_scalar(member_type))
> - return false;
> + goto bad_member;
> }
> return true;
> +
> +bad_member:
> + if (bad)
> + *bad = member;
The bot is correct about the nested types, would be nice to return the
containing struct.
> + return false;
> +}
> +
> +bool btf_type_is_scalar_struct(struct bpf_verifier_env *env,
> + const struct btf *btf,
> + const struct btf_type *t, int rec)
> +{
Nit: all callers specify 'rec == 0', hide it as well and remove the parameter?
> + return btf_scalar_struct_walk(env, btf, t, rec, NULL);
> }
>
> enum kfunc_ptr_arg_type {
> @@ -14030,17 +14046,41 @@ static int check_kfunc_call(struct bpf_verifier_env *env, struct bpf_insn *insn,
> meta.func_id == special_kfunc_list[KF_bpf_res_spin_lock_irqsave]))
> __mark_reg_const_zero(env, ®s[BPF_REG_0]);
> } else if (btf_type_is_struct(t)) {
> + const struct btf_member *bad = NULL;
> +
> /*
> * The returned struct comes back as raw register bits modeled
> * as an unknown scalar, so it must contain only scalars:
> * otherwise a pointer field would be laundered into a scalar
> * and escape provenance and reference tracking.
> */
> - if (!btf_type_is_scalar_struct(env, desc_btf, t, 0)) {
> + if (!btf_scalar_struct_walk(env, desc_btf, t, 0, &bad)) {
> + const char *member_note = "";
> +
> verbose(env,
> "kernel function %s returns %s %s that is not composed of scalars\n",
> func_name, btf_type_str(t),
> btf_name_by_offset(desc_btf, t->name_off));
> + if (bad) {
> + const char *bad_name = btf_name_by_offset(desc_btf, bad->name_off);
> + const struct btf_type *bad_type;
> +
> + bad_type = btf_type_skip_modifiers(desc_btf, bad->type, NULL);
> + verbose(env, "member '%s' has type %s\n", bad_name,
> + btf_type_str(bad_type));
> + member_note = bpf_diag_fmt(
> + env, " Its member '%s' is %s, not a scalar.", bad_name,
> + btf_type_str(bad_type));
> + }
Nit: since we are going into some details with this message,
it seems appropriate to handle the case when bad == NULL,
but btf_scalar_struct_walk() returns false, saying that
the structure is more then 4 levels deep.
> + bpf_diag_program_structure(
> + env, insn_idx, "unsupported kernel function return type",
> + "Call a kernel function that returns only scalars by value.",
> + "%s() returns %s %s by value.%s "
> + "A by-value return arrives as raw register bits that the verifier "
> + "can only model as unknown scalars, so e.g. a pointer may lose "
> + "the provenance and reference tracking that make it safe to use.",
Nit: I think this description adds more confusion. I'd say something
like "Only kfuncs returning scalar values or arena pointers, or
structures composed of scalar values and arena pointers are
supported".
> + func_name, btf_type_str(t),
> + btf_name_by_offset(desc_btf, t->name_off), member_note);
> return -EINVAL;
> }
> mark_kfunc_ret_regs(env, regs, t->size);
next prev parent reply other threads:[~2026-08-24 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 14:49 [PATCH bpf-next 1/2] bpf: Record each half of a paired return value in verifier diagnostics Yonghong Song
2026-08-24 14:49 ` [PATCH bpf-next 2/2] bpf: Report which member makes a kfunc return type unsupported Yonghong Song
2026-08-24 15:35 ` bot+bpf-ci
2026-08-24 19:27 ` Eduard Zingerman [this message]
2026-08-24 20:44 ` Yonghong Song
2026-08-24 19:29 ` [PATCH bpf-next 1/2] bpf: Record each half of a paired return value in verifier diagnostics Eduard Zingerman
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=5add32b3e212f7bcc01eb920c51749ae6d2aafcd.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=kernel-team@fb.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox