From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: 9front@9front.org
Subject: Re: [9fans] Blocking on write
Date: Mon, 15 May 2017 17:12:22 +0100 [thread overview]
Message-ID: <CAOw7k5gA+PL07E7ThpendvY6fqppQV5GqCBXGEQ9-9w5FCEfEQ@mail.gmail.com> (raw)
In-Reply-To: <CAHL7psH-aOtzJk5o8r-ROFaQb3MzRi8HcJsd8ZToQCpF5yrcBQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
On 15 May 2017 at 16:46, Giacomo Tesio <giacomo@tesio.it> wrote:
> Shouldn't the waserror code check that the queue has been actually closed?
Either that or check errstr against Ehungup, since that's the exact error
it incurred.
The latter has the advantage of not obscuring a different error if the pipe
is closed
between the write and waserror, but with pipes there's not much except
interrupt, I suppose,
so it seems a minor race and perhaps the qclosed check is adequate.
[-- Attachment #2: Type: text/html, Size: 868 bytes --]
next prev parent reply other threads:[~2017-05-15 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 10:05 Giacomo Tesio
2017-05-15 10:32 ` Charles Forsyth
2017-05-15 13:36 ` Giacomo Tesio
2017-05-15 15:46 ` Giacomo Tesio
2017-05-15 16:12 ` Charles Forsyth [this message]
2017-05-17 15:46 ` Giacomo Tesio
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=CAOw7k5gA+PL07E7ThpendvY6fqppQV5GqCBXGEQ9-9w5FCEfEQ@mail.gmail.com \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).