From: Ken Brown <kbrown@cornell.edu>
To: "cygwin-developers@cygwin.com" <cygwin-developers@cygwin.com>
Subject: Re: O_PATH for FIFOs
Date: Thu, 27 Jun 2019 01:15:00 -0000 [thread overview]
Message-ID: <a24936fa-39a6-d176-7681-122419bd9cf0@cornell.edu> (raw)
In-Reply-To: <89a49fc8-0675-b39b-832c-fe9379c21a3d@cornell.edu>
On 6/26/2019 4:09 PM, Ken Brown wrote:
> On 6/26/2019 12:26 PM, Ken Brown wrote:
>> Hi Corinna,
>>
>> You recently added support for the O_PATH flag, but it doesn't work for FIFOs.
>> (I just noticed this because of a failing emacs test.) Was this deliberate or
>> just an oversight? If it was the latter, I'll be glad to add O_PATH support for
>> FIFOs. I assume this should be done both on master and on the cygwin-3_0-branch.
>
> No answer required. It looks like this is going to be pretty trivial. I'll
> just send the patches.
For the record, the problem is that opening a FIFO with O_PATH hangs. I've just
sent a patch for the cygwin-3_0-branch. I'll hold off on the master branch
until we finish dealing with that one.
Ken
prev parent reply other threads:[~2019-06-27 1:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 16:26 Ken Brown
2019-06-26 20:09 ` Ken Brown
2019-06-27 1:15 ` Ken Brown [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=a24936fa-39a6-d176-7681-122419bd9cf0@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-developers@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).