From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Seems like a bug with mkfifo -m
Date: Thu, 28 May 2020 09:16:47 -0400 [thread overview]
Message-ID: <c117921e-388a-2ac2-dd95-3d66a6dae5be@cornell.edu> (raw)
In-Reply-To: <1562427636.19173685.1590653523730.JavaMail.zimbra@office.targem.ru>
On 5/28/2020 4:12 AM, Дмитрий Есарев via Cygwin wrote:
> Hi, all
>
> When i ran cygwin 2.x, i used mkfifo -m 0600 file to create a named pipe with no user and group permissions.
>
> in the latest cygwin the above command creates device with 0644 permissions. And i cant drop it to 0600:
>
> cygcheck.exe -V
> cygcheck (cygwin) 3.1.4
>
> $ umask 0077
> $ touch somefile; ls -l somefile
> -rw------- 1 admin absent 0 may 26 18:15 somefile
>
> $ mkfifo -m 0600 somefifo; ls -l somefifo
> prw-r--r-- 1 admin absent 0 may 26 18:16 somefifo
>
> $ chmod 600 somefifo; ls -l somefifo
> prw-r--r-- 1 admin absent 0 may 26 18:16 somefifo
>
>
>
> In old-good cygwin 2.x the command works as expected:
>
> $ cygcheck.exe -V
> cygcheck (cygwin) 2.9.0
>
> $ umask
> 0022
>
> $ mkfifo -m 0600 somefifo; ls -l somefifo
> prw------- 1 builduser Domain Users 0 May 26 18:21 somefifo
Thanks for the report. The problem isn't with mkfifo, it's with the permission
information reported by ls. I did a bisection of the Cygwin development repo
and found that the regression was introduced by the following commit:
commit f36262d56ac78f04de147746ce4a85c6155e4a23
Author: Corinna Vinschen <corinna@vinschen.de>
Date: Wed Jan 29 15:14:05 2020 +0100
Cygwin: stat: fix st_mode of fifos
I'll take a look if Corinna doesn't get to it first.
Ken
next prev parent reply other threads:[~2020-05-28 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1895966314.19173483.1590653374238.JavaMail.zimbra@office.targem.ru>
2020-05-28 8:12 ` Дмитрий Есарев
2020-05-28 13:16 ` Ken Brown [this message]
2020-05-28 14:52 ` Corinna Vinschen
2020-05-28 15:28 ` Ken Brown
2020-05-28 17:35 ` Ken Brown
2020-05-28 17:31 ` yoshi kakbudto
2020-05-28 17:39 ` Ken Brown
2020-05-28 18:17 ` Corinna Vinschen
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=c117921e-388a-2ac2-dd95-3d66a6dae5be@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@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).