From: patchwork-bot+netdevbpf@kernel.org
To: Puranjay Mohan <puranjay@kernel.org>
Cc: bpf@vger.kernel.org, puranjay12@gmail.com, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net, martin.lau@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, emil@etsalapatis.com,
kernel-team@meta.com
Subject: Re: [PATCH bpf-next v3 00/10] bpf: Make KF_TRUSTED_ARGS default
Date: Fri, 02 Jan 2026 20:20:19 +0000 [thread overview]
Message-ID: <176738521902.3999999.8092738930277465797.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260102180038.2708325-1-puranjay@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 2 Jan 2026 10:00:26 -0800 you wrote:
> v2: https://lore.kernel.org/all/20251231171118.1174007-1-puranjay@kernel.org/
> Changes in v2->v3:
> - Fix documentation: add a new section for kfunc parameters (Eduard)
> - Remove all occurances of KF_TRUSTED from comments, etc. (Eduard)
> - Fix the netfilter kfuncs to drop dead NULL checks.
> - Fix selftest for netfilter kfuncs to check for verification failures
> and remove the runtime failure that are not possible after this
> changes
>
> [...]
Here is the summary with links:
- [bpf-next,v3,01/10] bpf: Make KF_TRUSTED_ARGS the default for all kfuncs
https://git.kernel.org/bpf/bpf-next/c/1a5c01d2508a
- [bpf-next,v3,02/10] bpf: Remove redundant KF_TRUSTED_ARGS flag from all kfuncs
https://git.kernel.org/bpf/bpf-next/c/7646c7afd9a9
- [bpf-next,v3,03/10] bpf: net: netfilter: drop dead NULL checks
https://git.kernel.org/bpf/bpf-next/c/bddaf9adda72
- [bpf-next,v3,04/10] bpf: xfrm: drop dead NULL check in bpf_xdp_get_xfrm_state()
https://git.kernel.org/bpf/bpf-next/c/cd1d60949143
- [bpf-next,v3,05/10] HID: bpf: drop dead NULL checks in kfuncs
https://git.kernel.org/bpf/bpf-next/c/8fe172fa305f
- [bpf-next,v3,06/10] selftests: bpf: Update kfunc_param_nullable test for new error message
https://git.kernel.org/bpf/bpf-next/c/df5004579bbd
- [bpf-next,v3,07/10] selftests: bpf: Update failure message for rbtree_fail
https://git.kernel.org/bpf/bpf-next/c/03cc77b10e00
- [bpf-next,v3,08/10] selftests: bpf: fix test_kfunc_dynptr_param
https://git.kernel.org/bpf/bpf-next/c/230b0118e416
- [bpf-next,v3,09/10] selftests: bpf: fix cgroup_hierarchical_stats
https://git.kernel.org/bpf/bpf-next/c/cf82580c86a9
- [bpf-next,v3,10/10] selftests: bpf: Fix test_bpf_nf for trusted args becoming default
https://git.kernel.org/bpf/bpf-next/c/cf503eb2c6c3
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-01-02 20:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 18:00 [PATCH bpf-next v3 00/10] bpf: Make KF_TRUSTED_ARGS default Puranjay Mohan
2026-01-02 18:00 ` [PATCH bpf-next v3 01/10] bpf: Make KF_TRUSTED_ARGS the default for all kfuncs Puranjay Mohan
2026-01-02 18:00 ` [PATCH bpf-next v3 02/10] bpf: Remove redundant KF_TRUSTED_ARGS flag from " Puranjay Mohan
2026-01-02 18:00 ` [PATCH bpf-next v3 03/10] bpf: net: netfilter: drop dead NULL checks Puranjay Mohan
2026-01-02 18:00 ` [PATCH bpf-next v3 04/10] bpf: xfrm: drop dead NULL check in bpf_xdp_get_xfrm_state() Puranjay Mohan
2026-01-02 18:00 ` [PATCH bpf-next v3 05/10] HID: bpf: drop dead NULL checks in kfuncs Puranjay Mohan
2026-01-02 18:00 ` [PATCH bpf-next v3 06/10] selftests: bpf: Update kfunc_param_nullable test for new error message Puranjay Mohan
2026-01-02 18:00 ` [PATCH bpf-next v3 07/10] selftests: bpf: Update failure message for rbtree_fail Puranjay Mohan
2026-01-02 18:00 ` [PATCH bpf-next v3 08/10] selftests: bpf: fix test_kfunc_dynptr_param Puranjay Mohan
2026-01-02 18:00 ` [PATCH bpf-next v3 09/10] selftests: bpf: fix cgroup_hierarchical_stats Puranjay Mohan
2026-01-02 18:00 ` [PATCH bpf-next v3 10/10] selftests: bpf: Fix test_bpf_nf for trusted args becoming default Puranjay Mohan
2026-01-02 20: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=176738521902.3999999.8092738930277465797.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=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=puranjay12@gmail.com \
--cc=puranjay@kernel.org \
/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