From: Yonghong Song <yonghong.song@linux.dev>
To: Eduard Zingerman <eddyz87@gmail.com>, 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 02/12] bpf: Add verifier support for 16-byte returns in R0:R2
Date: Thu, 9 Jul 2026 21:57:43 -0700 [thread overview]
Message-ID: <afd1fcb8-e091-4fa8-8c2c-f52f495ed329@linux.dev> (raw)
In-Reply-To: <ea6bd9922125d2e3967dae33a686cd7e42830b73.camel@gmail.com>
On 7/9/26 3:21 PM, Eduard Zingerman wrote:
> On Wed, 2026-07-08 at 13:09 -0700, Yonghong Song wrote:
>> LLVM 23 added support for returning a value in two registers for an
>> __int128, or a struct/union whose size is greater than 8 but not more
>> than 16 bytes. See LLVM patches [1] and [2].
>>
>> Before LLVM 23 the BPF backend could not return these values at all. A
>> by-value struct or union return (of any size) was rejected at compile
>> time with:
>>
>> error: aggregate returns are not supported
>>
>> and an __int128 return failed later in the backend with:
>>
>> fatal error: error in backend: unable to allocate function return #1
>>
>> Both are resolved in LLVM 23, which lowers such returns into the R0:R2
>> register pair.
>>
>> This patch is one of several preparation patches that build up
>> <=16 byte return support incrementally:
>> - the verifier R0:R2 modelling in this patch,
>> - the x86 JIT move and JIT-capability gate,
>> - precision-backtracking and live-register tracking of R2,
>> - forcing the JIT for such programs, and
>> - guarding the trampoline paths.
>> Finally, the patch "bpf: Enable 16-byte aggregate return types" enables
>> support for 16-byte returns.
> Nit: I think the above paragraphs belong to a cover letter.
Will add this to the cover letter.
>
>> This patch adds handling for '>8' byte returns in several places: BPF
>> subprogram returns (the main program, and both global and static
>> subprograms) and kfunc returns.
>>
>> [1] https://github.com/llvm/llvm-project/pull/190894
>> [2] https://github.com/llvm/llvm-project/pull/206876
>>
>> Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
>> ---
>> kernel/bpf/verifier.c | 93 ++++++++++++++++++++++++++++++++++++++++---
>> 1 file changed, 88 insertions(+), 5 deletions(-)
>>
>> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
>> index 3f34ce1a3107..03ffb5f839fa 100644
>> --- a/kernel/bpf/verifier.c
>> +++ b/kernel/bpf/verifier.c
>> @@ -424,6 +424,35 @@ static bool subprog_returns_void(struct bpf_verifier_env *env, int subprog)
>> return btf_type_is_void(type);
>> }
>>
>> +static bool bpf_ret_reg_pair(struct bpf_verifier_env *env, int subprog)
>> +{
>> + const struct btf_type *type, *func, *func_proto;
>> + const struct btf *btf = env->prog->aux->btf;
>> + u32 btf_id;
>> +
>> + if (!btf || !env->prog->aux->func_info)
>> + return false;
>> +
>> + btf_id = env->prog->aux->func_info[subprog].type_id;
>> +
>> + func = btf_type_by_id(btf, btf_id);
>> + if (!func)
>> + return false;
> `if (!func) return false` checks here and below are not necessary
> after BTF validation.
Ack. Will remove them.
>
>> +
>> + func_proto = btf_type_by_id(btf, func->type);
>> + if (!func_proto)
>> + return false;
>> +
>> + type = btf_type_skip_modifiers(btf, func_proto->type, NULL);
>> + if (!type)
>> + return false;
>> +
>> + if (btf_type_is_struct(type) || btf_type_is_scalar(type))
>> + return type->size > 8 && type->size <= 16;
>> +
>> + return false;
>> +}
>> +
>> static const char *subprog_name(const struct bpf_verifier_env *env, int subprog)
>> {
>> struct bpf_func_info *info;
>> @@ -9459,10 +9488,17 @@ static int check_func_call(struct bpf_verifier_env *env, struct bpf_insn *insn,
>> clear_caller_saved_regs(env, caller->regs);
>> invalidate_outgoing_stack_args(env, cur_func(env));
>>
>> - /* All non-void global functions return a 64-bit SCALAR_VALUE. */
>> + /*
>> + * A non-void global function returns a 64-bit SCALAR_VALUE in
>> + * R0, or a >8 byte SCALAR_VALUE in the R0:R2 register pair.
>> + */
>> if (!subprog_returns_void(env, subprog)) {
>> mark_reg_unknown(env, caller->regs, BPF_REG_0);
>> caller->regs[BPF_REG_0].subreg_def = DEF_NOT_SUBREG;
>> + if (bpf_ret_reg_pair(env, subprog)) {
>> + mark_reg_unknown(env, caller->regs, BPF_REG_2);
>> + caller->regs[BPF_REG_2].subreg_def = DEF_NOT_SUBREG;
>> + }
>> }
>>
>> if (env->subprog_info[subprog].might_throw) {
>> @@ -9825,6 +9861,13 @@ static int prepare_func_exit(struct bpf_verifier_env *env, int *insn_idx)
>> } else {
>> /* return to the caller whatever r0 had in the callee */
>> caller->regs[BPF_REG_0] = *r0;
>> + if (bpf_ret_reg_pair(env, callee->subprogno)) {
>> + if (callee->regs[BPF_REG_2].type == PTR_TO_STACK) {
> Let's consolidate all such checks in one place and not copy-paste them.
Will try to consolidate them together.
>
>> + verbose(env, "cannot return stack pointer to the caller\n");
>> + return -EINVAL;
>> + }
>> + caller->regs[BPF_REG_2] = callee->regs[BPF_REG_2];
>> + }
>> }
>>
>> /* for callbacks like bpf_loop or bpf_for_each_map_elem go back to callsite,
>> @@ -10745,6 +10788,18 @@ static void mark_btf_func_reg_size(struct bpf_verifier_env *env, u32 regno,
>> return __mark_btf_func_reg_size(env, cur_regs(env), regno, reg_size);
>> }
>>
>> +static void mark_kfunc_ret_reg_size(struct bpf_verifier_env *env,
>> + struct bpf_reg_state *regs, u32 size)
>> +{
>> + if (size > 8) {
>> + mark_btf_func_reg_size(env, BPF_REG_0, 8);
>> + mark_reg_unknown(env, regs, BPF_REG_2);
>> + regs[BPF_REG_2].subreg_def = DEF_NOT_SUBREG;
>> + } else {
>> + mark_btf_func_reg_size(env, BPF_REG_0, size);
>> + }
>> +}
> This function makes R2 handling very asymmetric compared to R0:
> - mark_reg_unknown() for r0 is done in check_kfunc_call()
> - DEF_NOT_SUBREG for r0 is done in mark_btf_func_reg_size()
>
> I think the code should be structured to keep R0 and R2 processing
> uniform.
Ack
>
>> +
>> static bool is_kfunc_acquire(struct bpf_kfunc_call_arg_meta *meta)
>> {
>> return meta->kfunc_flags & KF_ACQUIRE;
>> @@ -13208,7 +13263,22 @@ static int check_kfunc_call(struct bpf_verifier_env *env, struct bpf_insn *insn,
>> if (meta.btf == btf_vmlinux && (meta.func_id == special_kfunc_list[KF_bpf_res_spin_lock] ||
>> meta.func_id == special_kfunc_list[KF_bpf_res_spin_lock_irqsave]))
>> __mark_reg_const_zero(env, ®s[BPF_REG_0]);
>> - mark_btf_func_reg_size(env, BPF_REG_0, t->size);
>> + mark_kfunc_ret_reg_size(env, regs, t->size);
>> + } else if (btf_type_is_struct(t)) {
>> + /*
>> + * 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)) {
>> + 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));
> Should this also check the size of the struct?
Later on, there is a size condition for struct (<= 16), so we should be okay here.
>
>> + return -EINVAL;
>> + }
>> + mark_reg_unknown(env, regs, BPF_REG_0);
>> + mark_kfunc_ret_reg_size(env, regs, t->size);
>> } else if (btf_type_is_ptr(t)) {
>> ptr_type = btf_type_skip_modifiers(desc_btf, t->type, &ptr_type_id);
>> err = check_special_kfunc(env, &meta, regs, insn_aux, ptr_type, desc_btf);
> [...]
next prev parent reply other threads:[~2026-07-10 4:58 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 20:09 [PATCH bpf-next 00/12] bpf: Support 16-byte return values in the R0:R2 register pair Yonghong Song
2026-07-08 20:09 ` [PATCH bpf-next 01/12] bpf: Factor check_global_ret_scalar_reg() out of the global return check Yonghong Song
2026-07-08 20:09 ` [PATCH bpf-next 02/12] bpf: Add verifier support for 16-byte returns in R0:R2 Yonghong Song
2026-07-08 21:17 ` bot+bpf-ci
2026-07-09 16:40 ` Yonghong Song
2026-07-09 22:21 ` Eduard Zingerman
2026-07-10 4:57 ` Yonghong Song [this message]
2026-07-08 20:09 ` [PATCH bpf-next 03/12] bpf: Wire up JIT support for 16-byte kfunc returns Yonghong Song
2026-07-10 0:06 ` Eduard Zingerman
2026-07-08 20:10 ` [PATCH bpf-next 04/12] bpf: Track R2 of register-pair returns in precision backtracking Yonghong Song
2026-07-08 21:10 ` bot+bpf-ci
2026-07-09 16:41 ` Yonghong Song
2026-07-10 0:31 ` Eduard Zingerman
2026-07-08 20:10 ` [PATCH bpf-next 05/12] bpf: Account R2 of register-pair returns in live register analysis Yonghong Song
2026-07-08 21:10 ` bot+bpf-ci
2026-07-09 21:07 ` Eduard Zingerman
2026-07-10 5:06 ` Yonghong Song
2026-07-08 20:10 ` [PATCH bpf-next 06/12] bpf: Force JIT for programs using the R0:R2 register pair Yonghong Song
2026-07-08 21:10 ` bot+bpf-ci
2026-07-09 3:15 ` Leon Hwang
2026-07-09 16:44 ` Yonghong Song
2026-07-09 20:30 ` Eduard Zingerman
2026-07-10 5:07 ` Yonghong Song
2026-07-09 22:27 ` Eduard Zingerman
2026-07-10 5:09 ` Yonghong Song
2026-07-08 20:10 ` [PATCH bpf-next 07/12] bpf: Reject >8 byte return values on return-reading trampoline paths Yonghong Song
2026-07-09 3:16 ` Leon Hwang
2026-07-09 16:52 ` Yonghong Song
2026-07-10 2:01 ` Leon Hwang
2026-07-09 23:08 ` Eduard Zingerman
2026-07-10 2:02 ` Leon Hwang
2026-07-10 5:27 ` Yonghong Song
2026-07-10 5:12 ` Yonghong Song
2026-07-08 20:10 ` [PATCH bpf-next 08/12] bpf: Enable 16-byte aggregate return types Yonghong Song
2026-07-08 20:28 ` sashiko-bot
2026-07-09 19:40 ` Yonghong Song
2026-07-10 0:45 ` Eduard Zingerman
2026-07-10 5:29 ` Yonghong Song
2026-07-08 20:10 ` [PATCH bpf-next 09/12] selftests/bpf: Add C tests for 16-byte returns in R0:R2 Yonghong Song
2026-07-08 20:24 ` sashiko-bot
2026-07-09 19:51 ` Yonghong Song
2026-07-08 21:10 ` bot+bpf-ci
2026-07-09 19:54 ` Yonghong Song
2026-07-10 1:19 ` Eduard Zingerman
2026-07-10 5:32 ` Yonghong Song
2026-07-08 20:10 ` [PATCH bpf-next 10/12] selftests/bpf: Add inline-asm and subprog tests for R0:R2 returns Yonghong Song
2026-07-08 20:28 ` sashiko-bot
2026-07-09 19:57 ` Yonghong Song
2026-07-10 1:38 ` Eduard Zingerman
2026-07-10 5:35 ` Yonghong Song
2026-07-08 20:10 ` [PATCH bpf-next 11/12] selftests/bpf: Cover tracing on >8 and <=16 byte return targets Yonghong Song
2026-07-08 20:10 ` [PATCH bpf-next 12/12] Documentation/bpf: Document 16-byte kfunc return values in R0:R2 Yonghong Song
2026-07-10 0:56 ` [PATCH bpf-next 00/12] bpf: Support 16-byte return values in the R0:R2 register pair Eduard Zingerman
2026-07-10 6:00 ` Yonghong Song
2026-07-10 6:13 ` Eduard Zingerman
2026-07-10 15:18 ` Yonghong Song
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=afd1fcb8-e091-4fa8-8c2c-f52f495ed329@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.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