On 08/06, Pavel Emelyanov wrote: > > If task X is exiting and has already exit_task_namespaces()-ed task > Y will OOPs during its exit in determining parent's namespace. I agree > that in that case this is not important what namespace X belongs to, > but we need to handle the race with changing the nsproxy from not-NULL > to NULL. This is OK to make this under task_lock() but what to add > extra locking for if we can avoid it? No, we can't take task_lock() under write_lock(tasklist). Oleg. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
