From: patchwork-bot+netdevbpf@kernel.org
To: Amery Hung <ameryhung@gmail.com>
Cc: bpf@vger.kernel.org, alexei.starovoitov@gmail.com,
andrii@kernel.org, daniel@iogearbox.net, eddyz87@gmail.com,
memxor@gmail.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v1 00/22] bpf: Unify helper and kfunc argument checks
Date: Sat, 12 Sep 2026 03:20:21 +0000 [thread overview]
Message-ID: <178918322113.3208623.7651069330846979270.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260905220117.922028-1-ameryhung@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 5 Sep 2026 15:00:55 -0700 you wrote:
> Hi,
>
> This is the 3rd and final patchset unifying helepr and kfunc checks.
>
> Helper and kfunc calls currently validate arguments through separate
> loops despite enforcing many of the same contracts. This duplicates
> type admission, nullability, memory, BTF, packet-access, and resource
> ownership handling.
>
> [...]
Here is the summary with links:
- [bpf-next,v1,01/22] bpf: Pass call metadata through shared argument checks
(no matching commit)
- [bpf-next,v1,02/22] bpf: Address check_func_arg() arguments by argno
(no matching commit)
- [bpf-next,v1,03/22] bpf: Only compare func_id against BPF_FUNC_* for helper calls
https://git.kernel.org/bpf/bpf-next/c/d18bcf4537e0
- [bpf-next,v1,04/22] bpf: Only compare func_id against kfunc BTF IDs for kfunc calls
https://git.kernel.org/bpf/bpf-next/c/0bddc59e33a4
- [bpf-next,v1,05/22] bpf: Rename ambiguous function argument types
(no matching commit)
- [bpf-next,v1,06/22] bpf: Unify kfunc argument kinds with enum bpf_arg_type
(no matching commit)
- [bpf-next,v1,07/22] bpf: Align helper and kfunc ARG_PTR_TO_PROG_AUX handling
(no matching commit)
- [bpf-next,v1,08/22] bpf: Classify kfunc arguments the verifier ignores
(no matching commit)
- [bpf-next,v1,09/22] bpf: Set OBJ_RELEASE when generating kfunc argument types
https://git.kernel.org/bpf/bpf-next/c/57e181cde7e6
- [bpf-next,v1,10/22] bpf: Set MEM_UNINIT and dynptr subtypes when generating kfunc arg types
https://git.kernel.org/bpf/bpf-next/c/78811eac7ae6
- [bpf-next,v1,11/22] bpf: Set MEM_RCU when generating kfunc argument types
(no matching commit)
- [bpf-next,v1,12/22] bpf: Resolve BTF ID of ARG_PTR_TO_BTF_ID in kfunc bpf_func_proto
(no matching commit)
- [bpf-next,v1,13/22] bpf: Resolve ARG_PTR_TO_MEM | MEM_FIXED_SIZE size in kfunc bpf_func_proto
https://git.kernel.org/bpf/bpf-next/c/6ca151e7cc32
- [bpf-next,v1,14/22] bpf: Consolidate runtime argument type resolution
(no matching commit)
- [bpf-next,v1,15/22] bpf: Consolidate nullable argument validation
(no matching commit)
- [bpf-next,v1,16/22] bpf: Drop redundant BTF pointer helper write rejection
(no matching commit)
- [bpf-next,v1,17/22] bpf: Consolidate helper and kfunc PTR_TO_BTF_ID argument matching
(no matching commit)
- [bpf-next,v1,18/22] bpf: Admit kfunc argument registers through check_reg_type()
(no matching commit)
- [bpf-next,v1,19/22] selftests/bpf: Test kfunc packet memory direct writes
(no matching commit)
- [bpf-next,v1,20/22] bpf: Consolidate function call pkt_access validation
https://git.kernel.org/bpf/bpf-next/c/8fe994c80af2
- [bpf-next,v1,21/22] bpf: Consolidate release argument validation
(no matching commit)
- [bpf-next,v1,22/22] bpf: Check helper and kfunc arguments in one path
(no matching commit)
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-12 3:21 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 22:00 [PATCH bpf-next v1 00/22] bpf: Unify helper and kfunc argument checks Amery Hung
2026-09-05 22:00 ` [PATCH bpf-next v1 01/22] bpf: Pass call metadata through shared " Amery Hung
2026-09-05 22:00 ` [PATCH bpf-next v1 02/22] bpf: Address check_func_arg() arguments by argno Amery Hung
2026-09-05 22:44 ` bot+bpf-ci
2026-09-09 17:37 ` Amery Hung
2026-09-05 22:00 ` [PATCH bpf-next v1 03/22] bpf: Only compare func_id against BPF_FUNC_* for helper calls Amery Hung
2026-09-05 22:00 ` [PATCH bpf-next v1 04/22] bpf: Only compare func_id against kfunc BTF IDs for kfunc calls Amery Hung
2026-09-05 22:44 ` bot+bpf-ci
2026-09-09 17:47 ` Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 05/22] bpf: Rename ambiguous function argument types Amery Hung
2026-09-05 23:08 ` bot+bpf-ci
2026-09-09 17:54 ` Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 06/22] bpf: Unify kfunc argument kinds with enum bpf_arg_type Amery Hung
2026-09-05 23:08 ` bot+bpf-ci
2026-09-09 18:04 ` Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 07/22] bpf: Align helper and kfunc ARG_PTR_TO_PROG_AUX handling Amery Hung
2026-09-05 23:08 ` bot+bpf-ci
2026-09-09 18:23 ` Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 08/22] bpf: Classify kfunc arguments the verifier ignores Amery Hung
2026-09-05 22:44 ` bot+bpf-ci
2026-09-09 18:27 ` Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 09/22] bpf: Set OBJ_RELEASE when generating kfunc argument types Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 10/22] bpf: Set MEM_UNINIT and dynptr subtypes when generating kfunc arg types Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 11/22] bpf: Set MEM_RCU when generating kfunc argument types Amery Hung
2026-09-05 22:44 ` bot+bpf-ci
2026-09-09 18:41 ` Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 12/22] bpf: Resolve BTF ID of ARG_PTR_TO_BTF_ID in kfunc bpf_func_proto Amery Hung
2026-09-05 23:08 ` bot+bpf-ci
2026-09-09 20:42 ` Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 13/22] bpf: Resolve ARG_PTR_TO_MEM | MEM_FIXED_SIZE size " Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 14/22] bpf: Consolidate runtime argument type resolution Amery Hung
2026-09-10 21:52 ` Alexei Starovoitov
2026-09-11 21:01 ` Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 15/22] bpf: Consolidate nullable argument validation Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 16/22] bpf: Drop redundant BTF pointer helper write rejection Amery Hung
2026-09-05 23:08 ` bot+bpf-ci
2026-09-09 20:48 ` Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 17/22] bpf: Consolidate helper and kfunc PTR_TO_BTF_ID argument matching Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 18/22] bpf: Admit kfunc argument registers through check_reg_type() Amery Hung
2026-09-05 23:23 ` bot+bpf-ci
2026-09-10 16:18 ` Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 19/22] selftests/bpf: Test kfunc packet memory direct writes Amery Hung
2026-09-05 22:44 ` bot+bpf-ci
2026-09-11 20:46 ` Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 20/22] bpf: Consolidate function call pkt_access validation Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 21/22] bpf: Consolidate release argument validation Amery Hung
2026-09-05 23:08 ` bot+bpf-ci
2026-09-11 20:47 ` Amery Hung
2026-09-05 22:01 ` [PATCH bpf-next v1 22/22] bpf: Check helper and kfunc arguments in one path Amery Hung
2026-09-05 22:33 ` sashiko-bot
2026-09-11 20:59 ` Amery Hung
2026-09-10 21:53 ` Alexei Starovoitov
2026-09-11 20:55 ` Amery Hung
2026-09-12 3:20 ` 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=178918322113.3208623.7651069330846979270.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@meta.com \
--cc=memxor@gmail.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