From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Frank van Maarseveen <frankvm@xs4all.nl>
Cc: Jesse Pollard <jesse@cats-chateau.net>,
Torin Ford <code-monkey@qwest.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.x Fork Problem?
Date: Fri, 13 Aug 2004 23:07:51 +0100 [thread overview]
Message-ID: <1092434870.25002.27.camel@localhost.localdomain> (raw)
In-Reply-To: <20040813190958.GB18563@janus>
On Gwe, 2004-08-13 at 20:09, Frank van Maarseveen wrote:
> > Yup - the parent process executed waitpid before the child process finished
> > the setup. This can happen in a multi-cpu environment or even a single, if
> > the scheduler puts the parent process higher than the child in the queue.
>
> ugh! I can follow the rationale for SMP.
Such a behaviour would not be rational, so we don't do anything like
that.
prev parent reply other threads:[~2004-08-13 23:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 0:01 2.6.x Fork Problem? Torin Ford
2004-08-12 12:08 ` Alan Cox
2004-08-12 14:26 ` Jesse Pollard
2004-08-13 19:09 ` Frank van Maarseveen
2004-08-13 19:36 ` Richard B. Johnson
2004-08-13 20:06 ` Frank van Maarseveen
2004-08-13 22:50 ` Torin Ford
2004-08-13 22:07 ` Alan Cox [this message]
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=1092434870.25002.27.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=code-monkey@qwest.net \
--cc=frankvm@xs4all.nl \
--cc=jesse@cats-chateau.net \
--cc=linux-kernel@vger.kernel.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