On Mon, Mar 16, 2015 at 3:50 PM, Thiago Macieira <thiago.macieira@xxxxxxxxx> wrote: > On Monday 16 March 2015 15:36:16 Kees Cook wrote: >> And just so I understand the races here, what happens in CLONE_FD >> (without CLONE_AUTOREAP) case where the child dies, but the parent >> never reads from the CLONE_FD fd, and closes it (or dies)? Will the >> modes switch that late in the child's lifetime? (i.e. even though the >> details were written to the fd, they were never read, yet it'll still >> switch and generate a SIGCHLD, etc?) > > What happens to a child that dies during the parent's lifetime but the parent > exits without reaping the child? > > The same should happen, whatever that behaviour is. Okay, sounds like the waitpid internals are tied to the read, not the child death. Perfect, that means it'll still be waitpid-able by whatever process inherits the zombie. Sounds good! Thanks for clarifying. :) -Kees -- Kees Cook Chrome OS Security -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
