RE: OT: fork(): parent or child should run first?


> Yes.
> But ATM the signal handler calls waitpid() and stores the pid in a
> to-be-cleaned-pids array (at time X).
> The main loop at some time in the future (say at time X+N) walks through
> the to-be-cleaned-pids array and cleans them from the active-childs
> array.

	Obviously that's broken. You would have precisely the same problem if you
did the same thing with file descriptors or sockets.

	DS


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

References:
- Re: OT: fork(): parent or child should run first?
  - From: Bernd Petrovitsch <[email protected]>

Prev by Date: RE: fork(): parent or child should run first?
Next by Date: Re: -mm seems significanty slower than mainline on kernbench
Previous by thread: Re: OT: fork(): parent or child should run first?
Next by thread: Re: OT: fork(): parent or child should run first?
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]