Re: [PATCH v3] cgroup: avoid flushing global workqueue in cgroup1_pidlist_destroy_all

[Tejun Heo]

On Tue, Sep 15, 2026 at 08:40:10PM +0800, Junnan Zhang wrote:
...
> To be upfront: I still have not reproduced the full 120s hang in the
> lab; the backlog and per-work latency I can build here remain well
> below the production node's. But the unpatched latency grows with
> exactly the two factors that were larger in production, while the
> patched latency is insensitive to them -- on an otherwise idle
> machine, with no competing workqueue items, no worker-creation stalls
> and no CPU contention.

That's a larger than two orders of magnitude gap. There likely were other, a
lot more important, factors.

Thanks.

-- 
tejun