Re: Patch: CLONE_PPID (was kernel thread support - LWP's)
Tim Hockin (thockin@isunix.it.ilstu.edu)
Tue, 20 Jul 1999 18:12:00 -0500 (CDT)
> >>> There may be code out there which gets confused on receiving a SIGCLD
> >>> for (or wait()ing on) a child which it doesn't remember creating.
> >>
> >>Any process can have children it doesn't know about creating, so this is not
> >>a
> >>new situation. It doesn't seem worth adding cruft to prevent.
> >
> > Are you prepared to give an example?
> >
>
> Sure:
> if (fork())
> execl("unsuspecting program");
> else
> {
> /* do things, exit when it's least expected */
> }
how is that having a child it doesn't know about? exec replaces the
current process, not forks another. And even if it did fork, the third
task would be a child of the second, not the first.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/