[lkml]   [2004]   [Jan]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: BUG: NTPL: waitpid() doesn't return?
On Sat, Jan 31, 2004 at 04:51:55PM +0100, Matthias Urlichs wrote:

> > Do you wait for all pids or for a specific one?
> >
> ... looking at the strace output, I see that thre are four different
> threads calling fork+child-exec/parent-waitpid() in parallel. The last
> one actually succeeds, so you might be right with this analysis.
> *Sigh* No matter how many people work at that code in the kernel, it's
> _still_ fragile. :-/

If they do not wait for a specific pid, the kernel is right. The kernel has
no way of knowing which process a specific waitpid is waiting for otherwise!

-- Open source, database driven DNS Software Linux Advanced Routing & Traffic Control HOWTO
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:00    [W:0.051 / U:1.432 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site