Hello, On Tue, May 23, 2023 at 12:42:46PM +0200, Christian Brauner wrote: ... > Nope, we're not putting namespace_sem in a header. The code it protects > is massively sensitive and it interacts with mount_lock and other locks. > This stays private to fs/namespace.c as far as I'm concerned. Michal, would it make sense to add a separate locking in cgroup.c? It'll add a bit more overhead but not massively so and we should be able to get similar gain without entangling with namespace locking. Thanks. -- tejun
