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 0/7] Unify helper and kfunc call_arg_meta
Date: Wed, 15 Jul 2026 09:10:17 +0000 [thread overview]
Message-ID: <178410661715.3974991.5935797358989431215.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260715064047.1793790-1-ameryhung@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Tue, 14 Jul 2026 23:40:40 -0700 you wrote:
> Hi all,
>
> I am working toward unifying helper and kfunc handling in the verifier.
> Historically, kfunc verification was mostly done separately from helper.
> This causes code/logic duplication and may introduce subtle bugs as the
> same checks are implemnented differently.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/7] bpf: Remove dynptr check in check_stack_range_initialized()
https://git.kernel.org/bpf/bpf-next/c/c28cbef2f898
- [bpf-next,v2,2/7] bpf: Factor out raw_mode-related fields in bpf_call_arg_meta
https://git.kernel.org/bpf/bpf-next/c/92ec8b1b6b24
- [bpf-next,v2,3/7] bpf: Pass argno to callees in check_func_arg() instead of argno_from_reg(regno)
https://git.kernel.org/bpf/bpf-next/c/77a4974c1749
- [bpf-next,v2,4/7] bpf: Unify helper and kfunc allocation-size argument handling
https://git.kernel.org/bpf/bpf-next/c/8faaa93b9f6a
- [bpf-next,v2,5/7] selftests/bpf: Test kfunc returning zero-sized allocation buffer
https://git.kernel.org/bpf/bpf-next/c/1e63cd6be055
- [bpf-next,v2,6/7] bpf: Drop redundant pkt_access from bpf_call_arg_meta
https://git.kernel.org/bpf/bpf-next/c/d55149ff8c85
- [bpf-next,v2,7/7] bpf: Unify helper and kfunc call argument meta
https://git.kernel.org/bpf/bpf-next/c/bf9c1b911f4d
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-07-15 9:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 6:40 [PATCH bpf-next v2 0/7] Unify helper and kfunc call_arg_meta Amery Hung
2026-07-15 6:40 ` [PATCH bpf-next v2 1/7] bpf: Remove dynptr check in check_stack_range_initialized() Amery Hung
2026-07-15 6:40 ` [PATCH bpf-next v2 2/7] bpf: Factor out raw_mode-related fields in bpf_call_arg_meta Amery Hung
2026-07-15 7:09 ` sashiko-bot
2026-07-15 7:48 ` bot+bpf-ci
2026-07-15 6:40 ` [PATCH bpf-next v2 3/7] bpf: Pass argno to callees in check_func_arg() instead of argno_from_reg(regno) Amery Hung
2026-07-15 6:40 ` [PATCH bpf-next v2 4/7] bpf: Unify helper and kfunc allocation-size argument handling Amery Hung
2026-07-15 6:40 ` [PATCH bpf-next v2 5/7] selftests/bpf: Test kfunc returning zero-sized allocation buffer Amery Hung
2026-07-15 6:40 ` [PATCH bpf-next v2 6/7] bpf: Drop redundant pkt_access from bpf_call_arg_meta Amery Hung
2026-07-15 6:40 ` [PATCH bpf-next v2 7/7] bpf: Unify helper and kfunc call argument meta Amery Hung
2026-07-15 7:00 ` sashiko-bot
2026-07-15 9: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=178410661715.3974991.5935797358989431215.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