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, eddyz87@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH bpf-next v4 00/15] bpf: Support by-value struct and __int128 arguments
Date: Sun, 13 Sep 2026 04:00:06 +0000 [thread overview]
Message-ID: <178927200638.3732794.3320350937871230371.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260912195156.980886-1-yonghong.song@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 12 Sep 2026 12:51:56 -0700 you wrote:
> A global function or a kfunc taking a struct or union by value is rejected
> today:
>
> Arg#1 type STRUCT in tar() is not supported yet.
> Unrecognized R2 type STRUCT
>
> and an __int128 argument is accepted but mis-counted: the compiler passes
> it in two registers while the verifier gives it one, so every argument
> after it is checked against the wrong register and the program is rejected
> for a register its source never names.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,01/15] bpf: Read a kfunc's __sz argument only when it is in a register
https://git.kernel.org/bpf/bpf-next/c/afe897e89918
- [bpf-next,v4,02/15] selftests/bpf: Add a test for an __int128 by-value argument
https://git.kernel.org/bpf/bpf-next/c/4196b1064bf2
- [bpf-next,v4,03/15] bpf: Rename bpf_subprog_info::arg_cnt to arg_slot_cnt
https://git.kernel.org/bpf/bpf-next/c/3bd9d96710f0
- [bpf-next,v4,04/15] bpf: Index global function arguments by argument slot
https://git.kernel.org/bpf/bpf-next/c/3f1023cab813
- [bpf-next,v4,05/15] bpf: Support by-value struct arguments up to 16 bytes
https://git.kernel.org/bpf/bpf-next/c/4dd676ca5b7a
- [bpf-next,v4,06/15] bpf: Support __int128 as a by-value function argument
https://git.kernel.org/bpf/bpf-next/c/00cfeb9554e2
- [bpf-next,v4,07/15] bpf: Rename bpf_call_summary::num_params to arg_slot_cnt
https://git.kernel.org/bpf/bpf-next/c/c6ff4e06033f
- [bpf-next,v4,08/15] bpf: Recognize by-value struct and __int128 kfunc arguments
https://git.kernel.org/bpf/bpf-next/c/ae6abae582b7
- [bpf-next,v4,09/15] bpf: Prepare kfunc arguments for the JIT from an ABI description
https://git.kernel.org/bpf/bpf-next/c/1e6c598b02e7
- [bpf-next,v4,10/15] bpf, x86: Move kfunc arguments into the x86-64 calling convention
https://git.kernel.org/bpf/bpf-next/c/a3195057406f
- [bpf-next,v4,11/15] bpf, arm64: Place trampoline arguments by the arm64 calling convention
https://git.kernel.org/bpf/bpf-next/c/afdbb4cdd3d2
- [bpf-next,v4,12/15] bpf, arm64: Move kfunc arguments into the arm64 calling convention
https://git.kernel.org/bpf/bpf-next/c/e1891a2c6474
- [bpf-next,v4,13/15] selftests/bpf: Add C tests for by-value arguments up to 16 bytes
https://git.kernel.org/bpf/bpf-next/c/9b55be31d16d
- [bpf-next,v4,14/15] selftests/bpf: Add inline-asm tests for by-value arguments
https://git.kernel.org/bpf/bpf-next/c/a7a97c37c58f
- [bpf-next,v4,15/15] selftests/bpf: Add tests for by-value kfunc arguments
https://git.kernel.org/bpf/bpf-next/c/4006c4b06c2c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-13 4:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 19:51 [PATCH bpf-next v4 00/15] bpf: Support by-value struct and __int128 arguments Yonghong Song
2026-09-12 19:52 ` [PATCH bpf-next v4 01/15] bpf: Read a kfunc's __sz argument only when it is in a register Yonghong Song
2026-09-12 20:06 ` sashiko-bot
2026-09-13 2:40 ` Yonghong Song
2026-09-12 19:52 ` [PATCH bpf-next v4 02/15] selftests/bpf: Add a test for an __int128 by-value argument Yonghong Song
2026-09-12 19:52 ` [PATCH bpf-next v4 03/15] bpf: Rename bpf_subprog_info::arg_cnt to arg_slot_cnt Yonghong Song
2026-09-12 19:52 ` [PATCH bpf-next v4 04/15] bpf: Index global function arguments by argument slot Yonghong Song
2026-09-12 19:52 ` [PATCH bpf-next v4 05/15] bpf: Support by-value struct arguments up to 16 bytes Yonghong Song
2026-09-12 19:52 ` [PATCH bpf-next v4 06/15] bpf: Support __int128 as a by-value function argument Yonghong Song
2026-09-12 19:52 ` [PATCH bpf-next v4 07/15] bpf: Rename bpf_call_summary::num_params to arg_slot_cnt Yonghong Song
2026-09-12 19:52 ` [PATCH bpf-next v4 08/15] bpf: Recognize by-value struct and __int128 kfunc arguments Yonghong Song
2026-09-12 19:52 ` [PATCH bpf-next v4 09/15] bpf: Prepare kfunc arguments for the JIT from an ABI description Yonghong Song
2026-09-12 20:10 ` sashiko-bot
2026-09-12 19:52 ` [PATCH bpf-next v4 10/15] bpf, x86: Move kfunc arguments into the x86-64 calling convention Yonghong Song
2026-09-12 19:52 ` [PATCH bpf-next v4 11/15] bpf, arm64: Place trampoline arguments by the arm64 " Yonghong Song
2026-09-13 2:47 ` Yonghong Song
2026-09-12 19:52 ` [PATCH bpf-next v4 12/15] bpf, arm64: Move kfunc arguments into " Yonghong Song
2026-09-12 19:53 ` [PATCH bpf-next v4 13/15] selftests/bpf: Add C tests for by-value arguments up to 16 bytes Yonghong Song
2026-09-12 19:53 ` [PATCH bpf-next v4 14/15] selftests/bpf: Add inline-asm tests for by-value arguments Yonghong Song
2026-09-12 19:53 ` [PATCH bpf-next v4 15/15] selftests/bpf: Add tests for by-value kfunc arguments Yonghong Song
2026-09-13 4:00 ` 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=178927200638.3732794.3320350937871230371.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=eddyz87@gmail.com \
--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 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.