BPF List
 help / color / mirror / Atom feed
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 v2 00/23] Unify helper and kfunc argument checks
Date: Sat, 12 Sep 2026 03:20:22 +0000	[thread overview]
Message-ID: <178918322237.3208623.2482210545600015868.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260911220415.1396439-1-ameryhung@gmail.com>

Hello:

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

On Fri, 11 Sep 2026 15:03:52 -0700 you wrote:
> Hi,
> 
> This is the third and final patchset unifying helper 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,v2,01/23] bpf: Pass call metadata through shared argument checks
    https://git.kernel.org/bpf/bpf-next/c/6523af719a21
  - [bpf-next,v2,02/23] bpf: Address check_func_arg() arguments by argno
    https://git.kernel.org/bpf/bpf-next/c/47f4215b8b54
  - [bpf-next,v2,03/23] bpf: Only compare func_id against BPF_FUNC_* for helper calls
    https://git.kernel.org/bpf/bpf-next/c/d18bcf4537e0
  - [bpf-next,v2,04/23] bpf: Only compare func_id against kfunc BTF IDs for kfunc calls
    https://git.kernel.org/bpf/bpf-next/c/0bddc59e33a4
  - [bpf-next,v2,05/23] bpf: Clarify unused and scalar function argument types
    https://git.kernel.org/bpf/bpf-next/c/6db166056c25
  - [bpf-next,v2,06/23] bpf: Unify kfunc argument kinds with enum bpf_arg_type
    https://git.kernel.org/bpf/bpf-next/c/5e7edfe68654
  - [bpf-next,v2,07/23] bpf: Classify kfunc arguments the verifier ignores
    https://git.kernel.org/bpf/bpf-next/c/5fa6e69e2e66
  - [bpf-next,v2,08/23] bpf: Align helper and kfunc ARG_PTR_TO_PROG_AUX handling
    https://git.kernel.org/bpf/bpf-next/c/0cc91f0e7241
  - [bpf-next,v2,09/23] bpf: Set OBJ_RELEASE when generating kfunc argument types
    https://git.kernel.org/bpf/bpf-next/c/57e181cde7e6
  - [bpf-next,v2,10/23] bpf: Set MEM_UNINIT and dynptr subtypes when generating kfunc arg types
    https://git.kernel.org/bpf/bpf-next/c/78811eac7ae6
  - [bpf-next,v2,11/23] bpf: Set MEM_RCU when generating kfunc argument types
    https://git.kernel.org/bpf/bpf-next/c/2b2b08c277cb
  - [bpf-next,v2,12/23] bpf: Resolve BTF ID of ARG_PTR_TO_BTF_ID in kfunc bpf_func_proto
    https://git.kernel.org/bpf/bpf-next/c/fb8d353bb58f
  - [bpf-next,v2,13/23] 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,v2,14/23] bpf: Consolidate runtime argument type resolution
    https://git.kernel.org/bpf/bpf-next/c/2e418779a00e
  - [bpf-next,v2,15/23] bpf: Consolidate nullable argument validation
    https://git.kernel.org/bpf/bpf-next/c/750f3770809a
  - [bpf-next,v2,16/23] bpf: Drop redundant BTF pointer helper write rejection
    https://git.kernel.org/bpf/bpf-next/c/a583d56e8de3
  - [bpf-next,v2,17/23] bpf: Consolidate helper and kfunc PTR_TO_BTF_ID argument matching
    https://git.kernel.org/bpf/bpf-next/c/b472f03e3141
  - [bpf-next,v2,18/23] bpf: Admit kfunc argument registers through check_reg_type()
    https://git.kernel.org/bpf/bpf-next/c/2bd4a975ea5d
  - [bpf-next,v2,19/23] bpf: Consolidate function call pkt_access validation
    https://git.kernel.org/bpf/bpf-next/c/8fe994c80af2
  - [bpf-next,v2,20/23] selftests/bpf: Test kfunc packet memory direct writes
    https://git.kernel.org/bpf/bpf-next/c/5647b77587ce
  - [bpf-next,v2,21/23] bpf: Consolidate release argument validation
    https://git.kernel.org/bpf/bpf-next/c/5dc1549afac9
  - [bpf-next,v2,22/23] selftests/bpf: Test nullable per-CPU kptr identity after exchange
    https://git.kernel.org/bpf/bpf-next/c/4f18de58a44c
  - [bpf-next,v2,23/23] bpf: Check helper and kfunc arguments in one path
    https://git.kernel.org/bpf/bpf-next/c/ab7fff217fd1

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-09-12  3:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 22:03 [PATCH bpf-next v2 00/23] Unify helper and kfunc argument checks Amery Hung
2026-09-11 22:03 ` [PATCH bpf-next v2 01/23] bpf: Pass call metadata through shared " Amery Hung
2026-09-11 22:03 ` [PATCH bpf-next v2 02/23] bpf: Address check_func_arg() arguments by argno Amery Hung
2026-09-11 22:03 ` [PATCH bpf-next v2 03/23] bpf: Only compare func_id against BPF_FUNC_* for helper calls Amery Hung
2026-09-11 22:03 ` [PATCH bpf-next v2 04/23] bpf: Only compare func_id against kfunc BTF IDs for kfunc calls Amery Hung
2026-09-11 22:03 ` [PATCH bpf-next v2 05/23] bpf: Clarify unused and scalar function argument types Amery Hung
2026-09-11 22:19   ` sashiko-bot
2026-09-11 22:03 ` [PATCH bpf-next v2 06/23] bpf: Unify kfunc argument kinds with enum bpf_arg_type Amery Hung
2026-09-11 22:26   ` sashiko-bot
2026-09-11 22:03 ` [PATCH bpf-next v2 07/23] bpf: Classify kfunc arguments the verifier ignores Amery Hung
2026-09-11 22:04 ` [PATCH bpf-next v2 08/23] bpf: Align helper and kfunc ARG_PTR_TO_PROG_AUX handling Amery Hung
2026-09-11 22:04 ` [PATCH bpf-next v2 09/23] bpf: Set OBJ_RELEASE when generating kfunc argument types Amery Hung
2026-09-11 22:04 ` [PATCH bpf-next v2 10/23] bpf: Set MEM_UNINIT and dynptr subtypes when generating kfunc arg types Amery Hung
2026-09-11 22:04 ` [PATCH bpf-next v2 11/23] bpf: Set MEM_RCU when generating kfunc argument types Amery Hung
2026-09-11 22:04 ` [PATCH bpf-next v2 12/23] bpf: Resolve BTF ID of ARG_PTR_TO_BTF_ID in kfunc bpf_func_proto Amery Hung
2026-09-11 22:04 ` [PATCH bpf-next v2 13/23] bpf: Resolve ARG_PTR_TO_MEM | MEM_FIXED_SIZE size " Amery Hung
2026-09-11 22:04 ` [PATCH bpf-next v2 14/23] bpf: Consolidate runtime argument type resolution Amery Hung
2026-09-11 22:04 ` [PATCH bpf-next v2 15/23] bpf: Consolidate nullable argument validation Amery Hung
2026-09-11 22:04 ` [PATCH bpf-next v2 16/23] bpf: Drop redundant BTF pointer helper write rejection Amery Hung
2026-09-11 22:04 ` [PATCH bpf-next v2 17/23] bpf: Consolidate helper and kfunc PTR_TO_BTF_ID argument matching Amery Hung
2026-09-11 22:04 ` [PATCH bpf-next v2 18/23] bpf: Admit kfunc argument registers through check_reg_type() Amery Hung
2026-09-11 22:04 ` [PATCH bpf-next v2 19/23] bpf: Consolidate function call pkt_access validation Amery Hung
2026-09-11 22:04 ` [PATCH bpf-next v2 20/23] selftests/bpf: Test kfunc packet memory direct writes Amery Hung
2026-09-11 22:36   ` sashiko-bot
2026-09-11 22:04 ` [PATCH bpf-next v2 21/23] bpf: Consolidate release argument validation Amery Hung
2026-09-11 22:04 ` [PATCH bpf-next v2 22/23] selftests/bpf: Test nullable per-CPU kptr identity after exchange Amery Hung
2026-09-11 22:04 ` [PATCH bpf-next v2 23/23] bpf: Check helper and kfunc arguments in one path 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=178918322237.3208623.2482210545600015868.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