public inbox for bpf@vger.kernel.org
 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, jose.marchesi@oracle.com,
	kernel-team@fb.com, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next v3 0/9] bpf: Prepare to support stack arguments
Date: Thu, 23 Apr 2026 15:10:18 +0000	[thread overview]
Message-ID: <177695701880.627354.70386758654770405.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260423033425.2536883-1-yonghong.song@linux.dev>

Hello:

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

On Wed, 22 Apr 2026 20:34:25 -0700 you wrote:
> The patch set prepares to support stack arguments for bpf functions
> and kfuncs. The major changes include:
>   - Avoid redundant calculation of bpf_reg_state. For stack
>     arguments, there exists no corresponding register number.
>   - Refactor check_kfunc_mem_size_reg() to have bpf_reg_state's
>     for both mem_reg and size_reg.
>   - Allow verifier logs to print stack arguments if there is no
>     corresponding register.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/9] bpf: Remove unused parameter from check_map_kptr_access()
    https://git.kernel.org/bpf/bpf-next/c/a7088176d829
  - [bpf-next,v3,2/9] bpf: Fix tail_call_reachable leak
    https://git.kernel.org/bpf/bpf-next/c/54c27ea6dadb
  - [bpf-next,v3,3/9] bpf: Remove WARN_ON_ONCE in check_kfunc_mem_size_reg()
    https://git.kernel.org/bpf/bpf-next/c/8a16c5b2b22f
  - [bpf-next,v3,4/9] bpf: Refactor to avoid redundant calculation of bpf_reg_state
    https://git.kernel.org/bpf/bpf-next/c/6a581b856c9e
  - [bpf-next,v3,5/9] bpf: Refactor to handle memory and size together
    https://git.kernel.org/bpf/bpf-next/c/024c0ab5db94
  - [bpf-next,v3,6/9] bpf: Rename existing argno to arg
    https://git.kernel.org/bpf/bpf-next/c/053a48cb2a54
  - [bpf-next,v3,7/9] bpf: Prepare verifier logs for upcoming kfunc stack arguments
    https://git.kernel.org/bpf/bpf-next/c/9b9f0b42703c
  - [bpf-next,v3,8/9] bpf: Introduce bpf register BPF_REG_PARAMS
    https://git.kernel.org/bpf/bpf-next/c/246ad6e5ee25
  - [bpf-next,v3,9/9] bpf: Reuse MAX_BPF_FUNC_ARGS for maximum number of arguments
    https://git.kernel.org/bpf/bpf-next/c/4439328d3878

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-04-23 15:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23  3:34 [PATCH bpf-next v3 0/9] bpf: Prepare to support stack arguments Yonghong Song
2026-04-23  3:34 ` [PATCH bpf-next v3 1/9] bpf: Remove unused parameter from check_map_kptr_access() Yonghong Song
2026-04-23  3:34 ` [PATCH bpf-next v3 2/9] bpf: Fix tail_call_reachable leak Yonghong Song
2026-04-23  3:34 ` [PATCH bpf-next v3 3/9] bpf: Remove WARN_ON_ONCE in check_kfunc_mem_size_reg() Yonghong Song
2026-04-23  3:34 ` [PATCH bpf-next v3 4/9] bpf: Refactor to avoid redundant calculation of bpf_reg_state Yonghong Song
2026-04-23  4:22   ` bot+bpf-ci
2026-04-23  3:34 ` [PATCH bpf-next v3 5/9] bpf: Refactor to handle memory and size together Yonghong Song
2026-04-23  3:34 ` [PATCH bpf-next v3 6/9] bpf: Rename existing argno to arg Yonghong Song
2026-04-23  3:35 ` [PATCH bpf-next v3 7/9] bpf: Prepare verifier logs for upcoming kfunc stack arguments Yonghong Song
2026-04-23  3:35 ` [PATCH bpf-next v3 8/9] bpf: Introduce bpf register BPF_REG_PARAMS Yonghong Song
2026-04-23  3:35 ` [PATCH bpf-next v3 9/9] bpf: Reuse MAX_BPF_FUNC_ARGS for maximum number of arguments Yonghong Song
2026-04-23  4:11   ` bot+bpf-ci
2026-04-23 15:10 ` 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=177695701880.627354.70386758654770405.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=jose.marchesi@oracle.com \
    --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