From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: test -r or -x always return false on an NFS mount?
Date: Thu, 15 Oct 2020 10:16:54 +0200 [thread overview]
Message-ID: <20201015081654.GE26704@calimero.vinschen.de> (raw)
In-Reply-To: <9e779a6f-288c-f9aa-615f-75f74192558a@emmenlauer.de>
On Oct 14 16:57, Mario Emmenlauer wrote:
> On 14.10.20 13:50, Corinna Vinschen wrote:
> > On Oct 14 11:06, Mario Emmenlauer wrote:
> >> On 14.10.20 10:28, Corinna Vinschen wrote:
> >>> Actually, not really. It's weird in fact, given ls(1) shows the
> >>> desired result. That would point to a bug in access(2), but there's
> >>> no special code in access(2) for NFS. For filesystems not supporting
> >>> ACLs (FAT, NFS, etc), it calls stat(2) and checks the st_mode bits
> >>> against the requested access(2) mode based on the uid/gid of the
> >>> caller, simple as that.
> >>
> >> Hmm, now that you mention it, I just coincidentally found an issue
> >> with the `_stat` call in Microsoft Windows 2004 update. In the Apache
> >
> > This is entirely unrelated. We're talking about Cygwin stat(2),
> > not msvcrt.dll _stat(). Different source, different call.
>
> Yes, but Cygwin stat is implemented based on the Win32 posix layer too,
> or not?
No, Cygwin is using the NT layer functions to access filesystems.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
prev parent reply other threads:[~2020-10-15 8:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 20:14 Mario Emmenlauer
2020-10-01 10:22 ` Mario Emmenlauer
2020-10-06 1:41 ` Ken Brown
2020-10-06 15:46 ` Andrey Repin
2020-10-06 16:10 ` Mario Emmenlauer
2020-10-13 18:36 ` Corinna Vinschen
2020-10-13 19:00 ` Mario Emmenlauer
2020-10-14 8:28 ` Corinna Vinschen
2020-10-14 9:06 ` Mario Emmenlauer
2020-10-14 11:50 ` Corinna Vinschen
2020-10-14 14:57 ` Mario Emmenlauer
2020-10-15 8:16 ` Corinna Vinschen [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=20201015081654.GE26704@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).