[Devel] Re: [PATCH] procfs: Do not release pid_ns->proc_mnt too early
Oleg Nesterov
oleg at redhat.com
Fri Jun 18 04:15:54 PDT 2010
On 06/18, Louis Rilling wrote:
>
> On 17/06/10 23:20 +0200, Oleg Nesterov wrote:
> > On 06/16, Louis Rilling wrote:
> > >
> > > Detached tasks are not seen by zap_pid_ns_processes()->sys_wait4(), so
> > > that release_task()->proc_flush_task() of container init can be called
> > > before it is for some detached tasks in the namespace.
> > >
> > > Pin proc_mnt's in copy_process(), so that proc_flush_task() becomes safe
> > > whatever the ordering of tasks.
> >
> > I must have missed something, but can't we just move mntput() ?
>
> See the log of the commit introducing pid_ns_release_proc() (6f4e6433):
>
> Sice the namespace holds the vfsmnt, vfsmnt holds the superblock and the
> superblock holds the namespace we must explicitly break this circle to destroy
> all the stuff. This is done after the init of the namespace dies.
I see thanks.
Besides, put_pid_ns() can be called in any context...
Oleg.
_______________________________________________
Containers mailing list
Containers at lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
More information about the Devel
mailing list