All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yonghong Song <yonghong.song@linux.dev>
To: bot+bpf-ci@kernel.org, bpf@vger.kernel.org
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
	eddyz87@gmail.com, kernel-team@fb.com, martin.lau@kernel.org,
	clm@meta.com, ihor.solodrai@linux.dev
Subject: Re: [PATCH bpf-next v2 06/13] bpf: Reject callbacks returning more than 8 bytes
Date: Sat, 8 Aug 2026 09:05:00 -0700	[thread overview]
Message-ID: <b9fe0394-bc46-4735-8584-51de6a96c076@linux.dev> (raw)
In-Reply-To: <2745ebef0f1c5b970d76736ab5828d4aea78433b2d3800b877f7e1a0555f4a4d@mail.kernel.org>



On 8/4/26 2:54 PM, bot+bpf-ci@kernel.org wrote:
>> commit 9c43eef7a91393c06822d44c361ee806f383cf97
>> Author: Yonghong Song <yonghong.song@linux.dev>
>>
>>      bpf: Reject callbacks returning more than 8 bytes
>>
>>      A callback handed to a helper or a kfunc (bpf_loop(),
>>      bpf_timer_set_callback(), bpf_for_each_map_elem(), ...) is invoked
>>      through bpf_callback_t, and an exception callback is invoked by
>>      bpf_throw() through
>>
>>        u64 (*bpf_exception_cb)(u64 cookie, u64 sp, u64 bp, u64, u64);
>>
>>      Both prototypes yield a single u64 in R0, and neither caller has any
>>      notion of a second return register, so a callback returning a value in
>>      the R0:R2 pair would have the upper half of its return value silently
>>      dropped.
>>
>>      Reject both at load time:
>>
>>       - check_ld_imm(): a callback is materialized as PTR_TO_FUNC by an
>>         ld_imm64 pointing at its subprogram, so the subprogram's return
>>         convention can be checked where the callback pointer is created,
>>         before it ever reaches a helper or kfunc argument.
>>
>>       - do_check_common(): an exception callback is not referenced by a
>>         PTR_TO_FUNC, it is named by a BTF decl_tag and verified on its own,
>>         so check it as its frame is set up, next to the existing "cannot
>>         return void" and single-argument checks.
>>
>>      Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
> This looks like a bug fix. Should this include:
>
>    Fixes: 63b5669f8a0d ("bpf: Add helpers to describe the R0:R2 return register pair")

There is no need to the bug fix. The actual R2 usage is in later patch
   Add verifier support for 16-byte returns in R0:R2

>
>
> ---
> AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
> See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md
>
> CI run summary: https://github.com/kernel-patches/bpf/actions/runs/30949310795


  reply	other threads:[~2026-08-08 16:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 20:35 [PATCH v2 00/13] bpf: Support aggregate return values up to 16 bytes Yonghong Song
2026-08-04 20:35 ` [PATCH bpf-next v2 01/13] bpf: Factor check_global_ret_scalar_reg() out of the global return check Yonghong Song
2026-08-04 20:35 ` [PATCH bpf-next v2 02/13] bpf: Add helpers to describe the R0:R2 return register pair Yonghong Song
2026-08-04 20:35 ` [PATCH bpf-next v2 03/13] bpf: Wire up JIT support for 16-byte kfunc returns Yonghong Song
2026-08-04 20:35 ` [PATCH bpf-next v2 04/13] bpf: Track R2 of register-pair returns in precision backtracking Yonghong Song
2026-08-04 20:35 ` [PATCH bpf-next v2 05/13] bpf: Account R2 of register-pair returns in live register analysis Yonghong Song
2026-08-04 21:14   ` sashiko-bot
2026-08-08 16:02     ` Yonghong Song
2026-08-04 20:35 ` [PATCH bpf-next v2 06/13] bpf: Reject callbacks returning more than 8 bytes Yonghong Song
2026-08-04 21:54   ` bot+bpf-ci
2026-08-08 16:05     ` Yonghong Song [this message]
2026-08-04 20:35 ` [PATCH bpf-next v2 07/13] bpf: Add verifier support for 16-byte returns in R0:R2 Yonghong Song
2026-08-04 20:52   ` sashiko-bot
2026-08-08 16:07     ` Yonghong Song
2026-08-04 20:36 ` [PATCH bpf-next v2 08/13] bpf: Reject register-pair returns when the subprog BTF is unreliable Yonghong Song
2026-08-04 20:36 ` [PATCH bpf-next v2 09/13] bpf: Enable aggregate return types up to 16 bytes Yonghong Song
2026-08-04 20:36 ` [PATCH bpf-next v2 10/13] selftests/bpf: Add C tests for 16-byte returns in R0:R2 Yonghong Song
2026-08-04 20:47   ` sashiko-bot
2026-08-08 16:30     ` Yonghong Song
2026-08-04 20:36 ` [PATCH bpf-next v2 11/13] selftests/bpf: Add inline-asm and subprog tests for R0:R2 returns Yonghong Song
2026-08-04 20:52   ` sashiko-bot
2026-08-08 16:35     ` Yonghong Song
2026-08-04 20:36 ` [PATCH bpf-next v2 12/13] selftests/bpf: Add tests for callbacks returning more than 8 bytes Yonghong Song
2026-08-04 20:36 ` [PATCH bpf-next v2 13/13] 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=b9fe0394-bc46-4735-8584-51de6a96c076@linux.dev \
    --to=yonghong.song@linux.dev \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bot+bpf-ci@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=clm@meta.com \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@kernel.org \
    /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.