From: bert hubert <ahu@ds9a.nl>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: NTPL: waitpid() doesn't return?
Date: Sat, 31 Jan 2004 17:18:05 +0100 [thread overview]
Message-ID: <20040131161805.GA15941@outpost.ds9a.nl> (raw)
In-Reply-To: <20040131155155.GA1504@kiste>
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!
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2004-01-31 16:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-31 10:46 BUG: NTPL: waitpid() doesn't return? Matthias Urlichs
2004-01-31 15:37 ` bert hubert
2004-01-31 15:51 ` Matthias Urlichs
2004-01-31 16:18 ` bert hubert [this message]
2004-01-31 18:15 ` Matthias Urlichs
2004-01-31 19:19 ` bert hubert
2004-01-31 20:49 ` Matthias Urlichs
2004-01-31 21:18 ` bert hubert
2004-01-31 21:41 ` Matthias Urlichs
2004-01-31 21:52 ` Roland McGrath
2004-01-31 19:02 ` Linus Torvalds
2004-01-31 20:00 ` Matthias Urlichs
2004-01-31 20:58 ` Linus Torvalds
2004-01-31 21:11 ` Matthias Urlichs
2004-01-31 22:52 ` Linus Torvalds
2004-01-31 22:29 ` Matthias Urlichs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040131161805.GA15941@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=smurf@smurf.noris.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.