Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@xxxxxxxxxx>:
On Fri, 6 Jun 2025 09:31:31 -0700 you wrote:
> Current cgroup prog ordering is appending at attachment time. This is not
> ideal. In some cases, users want specific ordering at a particular cgroup
> level. For example, in Meta, we have a case where three different
> applications all have cgroup/setsockopt progs and they require specific
> ordering. Current approach is to use a bpfchainer where one bpf prog
> contains multiple global functions and each global function can be
> freplaced by a prog for a specific application. The ordering of global
> functions decides the ordering of those application specific bpf progs.
> Using bpfchainer is a centralized approach and is not desirable as
> one of applications acts as a daemon. The decentralized attachment
> approach is more favorable for those applications.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/5] cgroup: Add bpf prog revisions to struct cgroup_bpf
https://git.kernel.org/bpf/bpf-next/c/9b8367b604c7
- [bpf-next,v5,2/5] bpf: Implement mprog API on top of existing cgroup progs
(no matching commit)
- [bpf-next,v5,3/5] libbpf: Support link-based cgroup attach with options
https://git.kernel.org/bpf/bpf-next/c/1d6711667cb3
- [bpf-next,v5,4/5] selftests/bpf: Move some tc_helpers.h functions to test_progs.h
https://git.kernel.org/bpf/bpf-next/c/c1bb68656bc1
- [bpf-next,v5,5/5] selftests/bpf: Add two selftests for mprog API based cgroup progs
https://git.kernel.org/bpf/bpf-next/c/e422d5f118e4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
