bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v5 06/11] bpf: Add verifier support for 16-byte returns in R0:R2
Date: Sun, 16 Aug 2026 20:44:48 -0700	[thread overview]
Message-ID: <f75fd498-047e-47e9-b8be-7ee7a4563825@linux.dev> (raw)
In-Reply-To: <c028bea425c3ea04df2156aec8a8b889fd6339ec.camel@gmail.com>



On 8/14/26 4:53 PM, Eduard Zingerman wrote:
> On Thu, 2026-08-13 at 13:02 -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 models that pair at calls to global and static BPF subprograms
>> and at kfunc calls: R2 is marked alongside R0 at the call, propagated out
>> of a callee at its exit, and held to the same scalar-only and no-stack-
>> pointer rules that R0 already is. A struct returned by a kfunc must be
>> composed of scalars, since its bytes reach the program as raw register
>> contents and a pointer field would otherwise be laundered into a scalar.
>>
>> An extension program is the one caller of the convention that cannot take
>> part in it: its own return value is the program exit code, read out of R0
>> alone, so it has no way to hand back an upper half. Replacing a function
>> whose return value is larger than 8 bytes is therefore rejected with
>> -EOPNOTSUPP rather than supported.
>>
>>    [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>
>> ---
> Acked-by: Eduard Zingerman <eddyz87@gmail.com>
>
>> @@ -19404,6 +19458,13 @@ int bpf_check_attach_target(struct bpf_verifier_log *log,
>>   			return -EOPNOTSUPP;
>>   		}
>>   
>> +		if (prog_extension && tgt_info->fmodel.ret_size > 8) {
>> +			bpf_log(log,
>> +				"Cannot replace function %s with a >8 byte return value\n",
>> +				tname);
>> +			return -EOPNOTSUPP;
>> +		}
>> +
> As commented in v4 [1], this check belongs to btf_check_type_match().
>
> [1] https://lore.kernel.org/bpf/e1bf30cac04d54aa328fee5282de348a89494048.camel@gmail.com/

Okay, will do.

>
>>   		/*
>>   		 * *.multi programs don't need an address during program
>>   		 * verification, we just take the module ref if needed.


  reply	other threads:[~2026-08-17  3:44 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 20:02 [PATCH bpf-next v5 00/11] bpf: Support aggregate return values up to 16 bytes Yonghong Song
2026-08-13 20:02 ` [PATCH bpf-next v5 01/11] bpf: Factor check_global_ret_scalar_reg() out of the global return check Yonghong Song
2026-08-14 22:24   ` Eduard Zingerman
2026-08-13 20:02 ` [PATCH bpf-next v5 02/11] bpf: Add helpers to describe the R0:R2 return register pair Yonghong Song
2026-08-13 21:11   ` bot+bpf-ci
2026-08-17  3:25     ` Yonghong Song
2026-08-14 22:43   ` Eduard Zingerman
2026-08-17  3:28     ` Yonghong Song
2026-08-13 20:02 ` [PATCH bpf-next v5 03/11] bpf: Wire up JIT support for 16-byte kfunc returns Yonghong Song
2026-08-14  1:20   ` sashiko-bot
2026-08-17  3:30     ` Yonghong Song
2026-08-13 20:02 ` [PATCH bpf-next v5 04/11] bpf: Track R2 of register-pair returns in precision backtracking Yonghong Song
2026-08-13 20:49   ` bot+bpf-ci
2026-08-17  3:32     ` Yonghong Song
2026-08-14 23:37   ` Eduard Zingerman
2026-08-17  3:33     ` Yonghong Song
2026-08-13 20:02 ` [PATCH bpf-next v5 05/11] bpf: Account R2 of register-pair returns in live register analysis Yonghong Song
2026-08-14  1:50   ` sashiko-bot
2026-08-17  3:35     ` Yonghong Song
2026-08-13 20:02 ` [PATCH bpf-next v5 06/11] bpf: Add verifier support for 16-byte returns in R0:R2 Yonghong Song
2026-08-13 21:11   ` bot+bpf-ci
2026-08-17  3:43     ` Yonghong Song
2026-08-14  2:26   ` sashiko-bot
2026-08-17  3:44     ` Yonghong Song
2026-08-14 23:53   ` Eduard Zingerman
2026-08-17  3:44     ` Yonghong Song [this message]
2026-08-13 20:02 ` [PATCH bpf-next v5 07/11] bpf: Enable aggregate return types up to 16 bytes Yonghong Song
2026-08-13 20:02 ` [PATCH bpf-next v5 08/11] bpf: Reject register-pair returns when the subprog BTF is unreliable Yonghong Song
2026-08-13 20:49   ` bot+bpf-ci
2026-08-17  3:47     ` Yonghong Song
2026-08-14  3:02   ` sashiko-bot
2026-08-17  3:49     ` Yonghong Song
2026-08-13 20:02 ` [PATCH bpf-next v5 09/11] selftests/bpf: Add C tests for 16-byte returns in R0:R2 Yonghong Song
2026-08-13 21:11   ` bot+bpf-ci
2026-08-17  3:50     ` Yonghong Song
2026-08-15  0:47   ` Eduard Zingerman
2026-08-17  3:53     ` Yonghong Song
2026-08-13 20:03 ` [PATCH bpf-next v5 10/11] selftests/bpf: Add inline-asm and subprog tests for R0:R2 returns Yonghong Song
2026-08-13 21:11   ` bot+bpf-ci
2026-08-17  3:59     ` Yonghong Song
2026-08-15  1:03   ` Eduard Zingerman
2026-08-17  4:00     ` Yonghong Song
2026-08-13 20:03 ` [PATCH bpf-next v5 11/11] Documentation/bpf: Document up to 16-byte kfunc return values in R0:R2 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=f75fd498-047e-47e9-b8be-7ee7a4563825@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;
as well as URLs for NNTP newsgroup(s).