From: Cedric Blancher <cedric.blancher@gmail.com>
To: cygwin@cygwin.com
Subject: Re: NFS mkfifo support in cygwin 3.5.0 Re: [ANNOUNCEMENT] cygwin 3.4.9-1
Date: Fri, 8 Sep 2023 06:48:00 +0200 [thread overview]
Message-ID: <CALXu0UcRuepZC_jH1+rzqLxDuhCtC4h94wgfVxkBxH9fSDEH7A@mail.gmail.com> (raw)
In-Reply-To: <CANH4o6MSXBxMBsqgtWbNe9rPETNgY-D5QxJO9AsLwe+tm0WkDw@mail.gmail.com>
On Thu, 7 Sept 2023 at 23:20, Martin Wege via Cygwin <cygwin@cygwin.com> wrote:
>
> On Wed, Sep 6, 2023 at 5:27 PM Corinna Vinschen via Cygwin-announce
> via Cygwin <cygwin@cygwin.com> wrote:
> >
> > The following packages have been uploaded to the Cygwin distribution:
> >
> > * cygwin-3.4.9-1
> > * cygwin-devel-3.4.9-1
> > * cygwin-doc-3.4.9-1
> >
> > Bug Fixes
> > ---------
> >
> > - Fix a bug introduced in cygwin 3.4.0 that switch_to_nat_pipe flag is
> > not cleared properly when non-cygwin app is terminated in the case
> > where pseudo console is not activated.
> >
> > - For the time being, disable creating special files using mknod/mkfifo
> > on NFS.
> > Addresses: https://cygwin.com/pipermail/cygwin/2023-August/254266.html
>
> While I am unhappy that you disabled this for Cygwin 3.4.9-1, we
> noticed that you added mkfifo support for Cygwin 3.5.0 in
> https://cygwin.com/git/?p=newlib-cygwin.git;a=commit;h=622fb0776ea333dd708ff312f08ec98311138fbe
> 🙏😁 :-)
>
> Thanks
>
> We are testing 3.5.0-0.423.g7ced682549ae.x86_64 - which includes
> 622fb0776ea333dd708ff312f08ec98311138fbe - right now, feedback will
> come on Monday
That's amazing news.
But an old bug crept in:
H is NFS file system
$ uname -a
CYGWIN_NT-10.0-19045 bastille0x44ef 3.5.0-0.423.g7ced682549ae.x86_64
2023-09-07 17:19 UTC x86_64 Cygwin
$ mount
C:/cygwin64/bin on /usr/bin type ntfs (binary,auto)
C:/cygwin64/lib on /usr/lib type ntfs (binary,auto)
C:/cygwin64 on / type ntfs (binary,auto)
C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)
H: on /cygdrive/h type nfs (binary,posix=0,user,noumount,auto)
M: on /cygdrive/m type nfs (binary,posix=0,user,noumount,auto)
N: on /cygdrive/n type nfs (binary,posix=0,user,noumount,auto)
O: on /cygdrive/o type nfs (binary,posix=0,user,noumount,auto)
P: on /cygdrive/p type nfs (binary,posix=0,user,noumount,auto)
$ cd /cygdrive/h/tmp/
$ mkfifo f1.fifo ; echo $?
0
$ mkfifo -m 0600 f2.fifo ; echo $?
mkfifo: cannot set permissions of 'f2.fifo': No such file or directory
1
So chmod() for a FIFO inode on NFS fails. Tested with MSFT NFSv3 and
new builds of the NFSv4.1 ms-nfs41-client filesystems.
Ced
--
Cedric Blancher <cedric.blancher@gmail.com>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
next prev parent reply other threads:[~2023-09-08 4:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 15:25 Corinna Vinschen via Cygwin-announce
2023-09-07 21:20 ` NFS mkfifo support in cygwin 3.5.0 " Martin Wege
2023-09-08 4:48 ` Cedric Blancher [this message]
2023-09-08 10:59 ` Corinna Vinschen
2023-09-08 20:31 ` Corinna Vinschen
2023-09-09 21:33 ` NFS mkfifo support in cygwin 3.5.0 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=CALXu0UcRuepZC_jH1+rzqLxDuhCtC4h94wgfVxkBxH9fSDEH7A@mail.gmail.com \
--to=cedric.blancher@gmail.com \
--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).