From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Teemu Koponen <tkoponen@iki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Opening of blocking FIFOs not reliable?
Date: Sun, 14 Aug 2005 01:49:24 +0100 [thread overview]
Message-ID: <1123980565.14138.21.camel@localhost.localdomain> (raw)
In-Reply-To: <c10854018590b2287bc64888d842a4ac@iki.fi>
On Gwe, 2005-08-12 at 20:18 -0700, Teemu Koponen wrote:
> the reader gets scheduled. Shouldn't the writer's open() block until
> the reader's open() is done?
Not neccessarily - but you are correct that it should lead to the
readers open completing and then EOFs being returned. Do you have a test
case for the problem?
Alan
next prev parent reply other threads:[~2005-08-14 0:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 3:18 Teemu Koponen
2005-08-14 0:49 ` Alan Cox [this message]
2005-08-14 10:15 Manfred Spraul
2005-08-14 10:40 ` Teemu Koponen
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=1123980565.14138.21.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tkoponen@iki.fi \
/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
Powered by JetHome