On 01/26, Daniel Hokka Zakrisson wrote: > > Serge E. Hallyn wrote: > > Ok, could you verify that the following patch at least solves > > the oopsing? > > > > (I can't reproduce the oops with Daniel's test prog) > > > > thanks, > > -serge > > Indeed, this patch solves the oopsing, but so did the last one. I think I > finally managed to figure out why too, as release_task would be called > with current referring to the parent process, or whoever is reaping the > process with the last reference to the namespace. Right? Not always. The task can do release_task() on itself if it is sub-thread, or its parent ignores SIGCHLD. Anyway I think your explanation is correct for this particular test-case. Oleg.