Jeremy Fitzhardinge wrote:
Eric W. Biederman wrote:
I'm guessing the issue is nash just calls wait and doesn't check the
returned pid value, assuming it is the only child it forked returning.
Which is valid except when you are running as pid == 1.

Hm, that's always a bug; a process can always have children it doesn't
expect (think forking, and then the parent execs).


Not if the process already forked.

But yes, in general this is a major screwup.

        -hpa
-
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/

Reply via email to