From: Stefano Lattarini <stefano.lattarini@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: David Barr <david.barr@cordelta.com>,
"bug-autoconf@gnu.org" <bug-autoconf@gnu.org>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Anders Kaseorg <andersk@MIT.EDU>
Subject: Re: [PATCH] t9010: Open backflow FIFO once to work around kernel race condition
Date: Wed, 27 Jun 2012 01:08:44 +0200 [thread overview]
Message-ID: <4FEA40FC.2080604@gmail.com> (raw)
In-Reply-To: <20120626224053.GA7155@burratino>
[Adding bug-autoconf]
On 06/27/2012 12:40 AM, Jonathan Nieder wrote:
> Hi,
>
> Quick first impressions:
>
> Anders Kaseorg wrote:
>
>> Sidestep this problem by opening the backflow FIFO once for
>> read+write.
>
> Is that portable?
>
According to the Autoconf manual, no:
Some shells, like ash, don't recognize bi-directional redirection (‘<>’).
And even on shells that recognize it, it is not portable to use on fifos:
Posix does not require read-write support for named pipes, and Cygwin
does not support it:
$ mkfifo fifo
$ exec 5<>fifo
$ echo hi >&5
bash: echo: write error: Communication error on send
But while the issue about Cygwin might still be relevant, the one about
ash seems to be out-of-date: I've verified that the "exec 5<>fifo"
command works with both dash 0.5.2 and dash 0.5.5.1 (that's why I'm
CC:ing bug-autoconf).
Regards,
Stefano
prev parent reply other threads:[~2012-06-26 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 22:30 [PATCH] t9010: Open backflow FIFO once to work around kernel race condition Anders Kaseorg
2012-06-26 22:40 ` Jonathan Nieder
2012-06-26 22:46 ` Anders Kaseorg
2012-06-26 22:58 ` Junio C Hamano
2012-06-26 23:08 ` Stefano Lattarini [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=4FEA40FC.2080604@gmail.com \
--to=stefano.lattarini@gmail.com \
--cc=andersk@MIT.EDU \
--cc=bug-autoconf@gnu.org \
--cc=david.barr@cordelta.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.