Re: [PATCH bpf-next 0/3] bpf, cgroup: Don't wait for cgroup_mutex to read or free cgroup bpf state

[patchwork-bot+netdevbpf@kernel.org]

Hello:

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

On Thu, 12 Nov 2026 09:27:12 -0800 you wrote:
> In the Meta fleet, BPF_PROG_QUERY callers, link-info readers and the
> cgroup bpf release work often wait minutes for cgroup_mutex. The holder is
> almost always a cgroup mkdir or rmdir stuck on kernfs_rwsem. In one day,
> hung-task reports showed this on 1,075 hosts (query), 94 hosts (link info)
> and 458 hosts (release work).
> 
> Patch 3 gives the cgroup bpf state its own mutex, so these paths no longer
> take cgroup_mutex. Attach, detach and replace still take cgroup_mutex
> first, because they walk the descendants.
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/3] bpf, cgroup: Don't read freed effective arrays in BPF_PROG_QUERY
    https://git.kernel.org/bpf/bpf/c/90f4e698f9c1
  - [bpf-next,2/3] bpf, cgroup: Don't attach to a removed cgroup
    https://git.kernel.org/bpf/bpf/c/b2e007371909
  - [bpf-next,3/3] bpf, cgroup: Protect cgroup_bpf state with its own mutex
    https://git.kernel.org/bpf/bpf/c/40aec6bab02e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html