BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] selftests/bpf: Fix tests for llvm23 true signature
Date: Wed, 10 Jun 2026 04:30:09 +0000	[thread overview]
Message-ID: <178106580939.2828762.10870449379729084922.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260609233402.2711071-1-yonghong.song@linux.dev>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Tue,  9 Jun 2026 16:34:02 -0700 you wrote:
> LLVM23 ([1]) records the 'true' function signature in BTF, i.e. the
> signature inferred after optimization rather than the one written in C.
> This caused two kinds of selftest failures (see below).
> 
> Case 1: keep int return type for tailcall subprogs
> 
> The verifier requires any subprog that issues a bpf_tail_call to return
> an 'int' (see check_btf_func() in kernel/bpf/check_btf.c, which rejects
> it with "tail_call is only allowed in functions that return 'int'").
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/2] selftests/bpf: Keep int return type for tailcall subprogs
    https://git.kernel.org/bpf/bpf-next/c/be1d838b88e4
  - [bpf-next,v2,2/2] selftests/bpf: Adjust fexit_bpf2bpf ctx layout for llvm23 true signature
    https://git.kernel.org/bpf/bpf-next/c/e775c522a455

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-06-10  4:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 23:34 [PATCH bpf-next v2 0/2] selftests/bpf: Fix tests for llvm23 true signature Yonghong Song
2026-06-09 23:34 ` [PATCH bpf-next v2 1/2] selftests/bpf: Keep int return type for tailcall subprogs Yonghong Song
2026-06-09 23:42   ` sashiko-bot
2026-06-10  3:41     ` Yonghong Song
2026-06-10  4:06     ` Yonghong Song
2026-06-10  0:07   ` bot+bpf-ci
2026-06-10  3:45     ` Yonghong Song
2026-06-09 23:34 ` [PATCH bpf-next v2 2/2] selftests/bpf: Adjust fexit_bpf2bpf ctx layout for llvm23 true signature Yonghong Song
2026-06-10  4:30 ` patchwork-bot+netdevbpf [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=178106580939.2828762.10870449379729084922.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@kernel.org \
    --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