From: "Matthias Urlichs" <smurf@smurf.noris.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: BUG: NTPL: waitpid() doesn't return?
Date: Sat, 31 Jan 2004 22:11:09 +0100 [thread overview]
Message-ID: <20040131211109.GC2160@kiste> (raw)
In-Reply-To: <Pine.LNX.4.58.0401311223110.2105@home.osdl.org>
Hi,
Linus Torvalds:
> The strace case I'm more than willing to pass off as a strace problem.
> I find it quite common that strace doesn't detach from processes, leaving
> some of them in a stopped state. So I assumed that the particular trace
> wasn't very interesting.
>
Hmm. "Unfortunately", the test program which bert posted DOES work
correctly under strace.
So there's definitely something fishy going on here.
> The bugs seems to be something totally different: you create a
> "CLONE_DETACHED" child, and then you expect to be able to wait for it.
That's not "me", that's "the fork() in the NPTL library".
Besides, bert's test program exhibits exactly the same clone()
arguments, yet it works ...
--
Matthias Urlichs | noris network AG | http://smurf.noris.de/
next prev parent reply other threads:[~2004-01-31 21:40 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
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 [this message]
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=20040131211109.GC2160@kiste \
--to=smurf@smurf.noris.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox