From: patchwork-bot+netdevbpf@kernel.org
To: Amery Hung <ameryhung@gmail.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
alexei.starovoitov@gmail.com, andrii@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, memxor@gmail.com,
martin.lau@kernel.org, shakeel.butt@linux.dev,
roman.gushchin@linux.dev, kuniyu@google.com,
kerneljasonxing@gmail.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v4 00/15] bpf: A common way to attach struct_ops to a cgroup
Date: Sat, 19 Sep 2026 05:40:10 +0000 [thread overview]
Message-ID: <178979641040.1277927.5226384464308914139.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260917200542.3689605-1-ameryhung@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 17 Sep 2026 13:05:26 -0700 you wrote:
> Hi,
>
> I am continuing Martin's work to support attaching struct_ops to cgroup.
>
> At LSF/MM/BPF 2025, Martin presented [1] the need for a new interface
> to extend tcp_sock operations instead of adding more BPF_SOCK_OPS_*CB
> enum values. The need for predictable ordering when attaching struct_ops
> to a cgroup was also briefly discussed.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,01/15] bpf: Remove __rcu tagging in st_link->map
https://git.kernel.org/bpf/bpf-next/c/012089512144
- [bpf-next,v4,02/15] bpf: Make struct_ops tasks_rcu grace period optional
https://git.kernel.org/bpf/bpf-next/c/5db69b0fbdc8
- [bpf-next,v4,03/15] bpf: Add bpf_struct_ops accessor helpers
https://git.kernel.org/bpf/bpf-next/c/3668bc410260
- [bpf-next,v4,04/15] bpf: Remove unnecessary prog_list_prog() check
https://git.kernel.org/bpf/bpf-next/c/1ef6cb2cc587
- [bpf-next,v4,05/15] bpf: Replace prog_list_prog() check with direct pl->prog and pl->link check
https://git.kernel.org/bpf/bpf-next/c/c6dde091dc12
- [bpf-next,v4,06/15] bpf: Add prog_list_init_item(), prog_list_replace_item(), and prog_list_id()
https://git.kernel.org/bpf/bpf-next/c/4d71b3e0821f
- [bpf-next,v4,07/15] bpf: Move LSM trampoline unlink into bpf_cgroup_link_auto_detach()
https://git.kernel.org/bpf/bpf-next/c/2ef54525d2fc
- [bpf-next,v4,08/15] bpf: Add a few bpf_cgroup_array_* helper functions
https://git.kernel.org/bpf/bpf-next/c/e176821b68d8
- [bpf-next,v4,09/15] bpf: Add infrastructure to support attaching struct_ops to cgroups
https://git.kernel.org/bpf/bpf-next/c/369d9dcd8fb8
- [bpf-next,v4,10/15] bpf: Allow all struct_ops to use bpf_dynptr_from_skb()
https://git.kernel.org/bpf/bpf-next/c/6d4ce907665d
- [bpf-next,v4,11/15] bpf: tcp: Support selected sock_ops callbacks as struct_ops
https://git.kernel.org/bpf/bpf-next/c/5ac77ae32940
- [bpf-next,v4,12/15] bpf: tcp: Support parse/len/write header option hooks in bpf_tcp_ops
https://git.kernel.org/bpf/bpf-next/c/3bb54768fe3e
- [bpf-next,v4,13/15] libbpf: Support attaching struct_ops to a cgroup
https://git.kernel.org/bpf/bpf-next/c/6bad848e3f70
- [bpf-next,v4,14/15] selftests/bpf: Test attaching struct_ops to a cgroup
https://git.kernel.org/bpf/bpf-next/c/ae7b5234fa8b
- [bpf-next,v4,15/15] selftests/bpf: Add test for bpf_tcp_ops header option hooks
https://git.kernel.org/bpf/bpf-next/c/d7399d91417b
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-09-19 5:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 20:05 [PATCH bpf-next v4 00/15] bpf: A common way to attach struct_ops to a cgroup Amery Hung
2026-09-17 20:05 ` [PATCH bpf-next v4 01/15] bpf: Remove __rcu tagging in st_link->map Amery Hung
2026-09-17 20:05 ` [PATCH bpf-next v4 02/15] bpf: Make struct_ops tasks_rcu grace period optional Amery Hung
2026-09-17 20:30 ` sashiko-bot
2026-09-17 21:34 ` bot+bpf-ci
2026-09-17 20:05 ` [PATCH bpf-next v4 03/15] bpf: Add bpf_struct_ops accessor helpers Amery Hung
2026-09-17 20:18 ` sashiko-bot
2026-09-17 21:16 ` bot+bpf-ci
2026-09-17 20:05 ` [PATCH bpf-next v4 04/15] bpf: Remove unnecessary prog_list_prog() check Amery Hung
2026-09-17 20:05 ` [PATCH bpf-next v4 05/15] bpf: Replace prog_list_prog() check with direct pl->prog and pl->link check Amery Hung
2026-09-17 20:05 ` [PATCH bpf-next v4 06/15] bpf: Add prog_list_init_item(), prog_list_replace_item(), and prog_list_id() Amery Hung
2026-09-17 20:05 ` [PATCH bpf-next v4 07/15] bpf: Move LSM trampoline unlink into bpf_cgroup_link_auto_detach() Amery Hung
2026-09-17 20:05 ` [PATCH bpf-next v4 08/15] bpf: Add a few bpf_cgroup_array_* helper functions Amery Hung
2026-09-17 20:05 ` [PATCH bpf-next v4 09/15] bpf: Add infrastructure to support attaching struct_ops to cgroups Amery Hung
2026-09-17 21:34 ` bot+bpf-ci
2026-09-17 20:05 ` [PATCH bpf-next v4 10/15] bpf: Allow all struct_ops to use bpf_dynptr_from_skb() Amery Hung
2026-09-17 20:05 ` [PATCH bpf-next v4 11/15] bpf: tcp: Support selected sock_ops callbacks as struct_ops Amery Hung
2026-09-17 21:34 ` bot+bpf-ci
2026-09-17 20:05 ` [PATCH bpf-next v4 12/15] bpf: tcp: Support parse/len/write header option hooks in bpf_tcp_ops Amery Hung
2026-09-17 21:34 ` bot+bpf-ci
2026-09-17 20:05 ` [PATCH bpf-next v4 13/15] libbpf: Support attaching struct_ops to a cgroup Amery Hung
2026-09-17 20:05 ` [PATCH bpf-next v4 14/15] selftests/bpf: Test " Amery Hung
2026-09-17 20:23 ` sashiko-bot
2026-09-17 21:34 ` bot+bpf-ci
2026-09-17 20:05 ` [PATCH bpf-next v4 15/15] selftests/bpf: Add test for bpf_tcp_ops header option hooks Amery Hung
2026-09-19 5: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=178979641040.1277927.5226384464308914139.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=kerneljasonxing@gmail.com \
--cc=kuniyu@google.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@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