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 v3 00/11] Unify subprog argument checks
Date: Tue, 29 Sep 2026 10:40:14 +0000	[thread overview]
Message-ID: <179067841453.421460.3752055362291528812.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260928185334.1004200-1-ameryhung@gmail.com>

Hello:

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

On Mon, 28 Sep 2026 11:53:23 -0700 you wrote:
> Hi,
> 
> Helper and kfunc calls now validate arguments through check_func_args(),
> while subprog calls still duplicate much of the same validation in
> btf_check_func_arg_match(). This makes common argument rules and
> diagnostics easy to change for one call kind without updating the other.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,01/11] bpf: Fix kfunc BTF parameter lookups after wide arguments
    https://git.kernel.org/bpf/bpf-next/c/d82229330a32
  - [bpf-next,v3,02/11] bpf: Identify subprog calls in argument metadata
    https://git.kernel.org/bpf/bpf-next/c/f7be720383d3
  - [bpf-next,v3,03/11] bpf: Build argument prototypes for subprog calls
    https://git.kernel.org/bpf/bpf-next/c/668a51c4ed4b
  - [bpf-next,v3,04/11] bpf: Check subprog scalar arguments in the common path
    https://git.kernel.org/bpf/bpf-next/c/c40f746cc7de
  - [bpf-next,v3,05/11] bpf: Check global subprog untrusted arguments in the common path
    https://git.kernel.org/bpf/bpf-next/c/3886a9fc38de
  - [bpf-next,v3,06/11] bpf: Check subprog context arguments in the common path
    https://git.kernel.org/bpf/bpf-next/c/03f312c2cbd5
  - [bpf-next,v3,07/11] bpf: Check subprog arena arguments in the common path
    https://git.kernel.org/bpf/bpf-next/c/44cfe492d06f
  - [bpf-next,v3,08/11] bpf: Check subprog dynptr arguments in the common path
    https://git.kernel.org/bpf/bpf-next/c/a1456ec685a6
  - [bpf-next,v3,09/11] bpf: Check global subprog BTF-ID arguments in the common path
    https://git.kernel.org/bpf/bpf-next/c/77d9384a69cd
  - [bpf-next,v3,10/11] bpf: Check global subprog memory arguments in the common path
    https://git.kernel.org/bpf/bpf-next/c/46e074462108
  - [bpf-next,v3,11/11] bpf: Check all subprog arguments in the common path
    https://git.kernel.org/bpf/bpf-next/c/bf82eb018328

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-29 10:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 18:53 [PATCH bpf-next v3 00/11] Unify subprog argument checks Amery Hung
2026-09-28 18:53 ` [PATCH bpf-next v3 01/11] bpf: Fix kfunc BTF parameter lookups after wide arguments Amery Hung
2026-09-28 18:53 ` [PATCH bpf-next v3 02/11] bpf: Identify subprog calls in argument metadata Amery Hung
2026-09-28 18:53 ` [PATCH bpf-next v3 03/11] bpf: Build argument prototypes for subprog calls Amery Hung
2026-09-28 18:53 ` [PATCH bpf-next v3 04/11] bpf: Check subprog scalar arguments in the common path Amery Hung
2026-09-28 18:53 ` [PATCH bpf-next v3 05/11] bpf: Check global subprog untrusted " Amery Hung
2026-09-28 18:53 ` [PATCH bpf-next v3 06/11] bpf: Check subprog context " Amery Hung
2026-09-28 18:53 ` [PATCH bpf-next v3 07/11] bpf: Check subprog arena " Amery Hung
2026-09-28 18:53 ` [PATCH bpf-next v3 08/11] bpf: Check subprog dynptr " Amery Hung
2026-09-28 18:53 ` [PATCH bpf-next v3 09/11] bpf: Check global subprog BTF-ID " Amery Hung
2026-09-28 18:53 ` [PATCH bpf-next v3 10/11] bpf: Check global subprog memory " Amery Hung
2026-09-28 19:53   ` bot+bpf-ci
2026-09-28 18:53 ` [PATCH bpf-next v3 11/11] bpf: Check all subprog " Amery Hung
2026-09-29 10:40 ` 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=179067841453.421460.3752055362291528812.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