mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Alvord <jalvo@mbay.net>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: "Mattias Engdegård" <f91-men@nada.kth.se>,
	pmenage@ensim.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] Pollable /proc/<pid>/ - avoid SIGCHLD/poll() races
Date: Sat, 13 Oct 2001 19:25:03 -0700	[thread overview]
Message-ID: <tothstsfpl2t6b92f58mj8bv5j6005t0p3@4ax.com> (raw)
In-Reply-To: <E15p3JS-0000ko-00@pmenage-dt.ensim.com> <200110041418.QAA17395@my.nada.kth.se> <20011013173619.C20499@kushida.jlokier.co.uk>
In-Reply-To: <20011013173619.C20499@kushida.jlokier.co.uk>

On Sat, 13 Oct 2001 17:36:19 +0200, Jamie Lokier
<lk@tantalophile.demon.co.uk> wrote:

>Mattias Engdegård wrote:
>> I don't think it's contrived --- writing not a byte, but the pid and
>> return status of the dead child to a pipe is an old but useful trick.
>> It gives a natural serialisation of child deaths, and also eliminates
>> the common race where a child dies before its parent has recorded its
>> pid in a data structure. See it as a safe way of converting an
>> asynchronous signal to a queued event.
>>
>> Using pipes to wake up blocking select()s is a useful thing in general,
>> and often a lot cleaner than using signals when dealing with threads.
>
>This mistake is exactly the reason that Netscape 4.x freezes from time
>to time on Linux.
>
>It tries to write too many things to a pipe, making the assumption that
>this will never happen.

At one point a few years ago, someone implemented a loadable library
which "fixed" the Netscape problem by knowing what the bug was, doing
things the right way, and presenting the interface Netscape expected.

john

      reply	other threads:[~2001-10-14  2:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-04  7:52 Paul Menage
2001-10-04  8:59 ` Christoph Rohland
2001-10-04  9:31   ` Paul Menage
2001-10-04 10:25     ` Christoph Rohland
2001-10-13 15:44     ` Jamie Lokier
2001-10-04 14:18 ` Mattias Engdegård
2001-10-04 20:39   ` Paul Menage
2001-10-05  9:36     ` Mattias Engdegård
2001-10-13 15:36   ` Jamie Lokier
2001-10-14  2:25     ` John Alvord [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=tothstsfpl2t6b92f58mj8bv5j6005t0p3@4ax.com \
    --to=jalvo@mbay.net \
    --cc=f91-men@nada.kth.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk@tantalophile.demon.co.uk \
    --cc=pmenage@ensim.com \
    /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

all inboxes | Powered by JetHome®