On Wed, 2007-01-17 at 15:30 -0700, Eric W. Biederman wrote: > Cedric Le Goater <[EMAIL PROTECTED]> writes: > > > > your first analysis was correct : exit_task_namespaces() should be moved > > above exit_notify(tsk). It will require some extra fixes for nsproxy > > though. > > I think the only issue is the child_reaper and currently we only have one of > those. When we really do the pid namespace we are going to have to revisit > this. My gut feel says that we won't be able to exit our pid namespace until > the process is waited on. So we may need to break up exit_task_namespace into > individual components.
It makes little sense, afaics, to have an interruptible sleep in something like lockd_down() if you have no pid space or signal handling. That isn't the only place where the process has to wait in an NFS unmount, BTW. Things like rpc client cleanup (waiting for all the RPC tasks to complete) also tend to lead to interruptible sleeps. Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
