X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DB8D53850214
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1692364184;
	bh=fp6eSTbwIy+VwFaK+gXkk8fjbhucUD8EL7IvUic+qco=;
	h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=sjqtZlMTgMsDUMvw3L2Z0WLAqdgwvuH+ZN8d2YGnz9Lxuy+YYivzRp7tc8xvxcvTT
	 jMtxVvfHUK/Px9puPpD/Ymz26qZdNzkqifPC85kTu5d7bsq8DLXMxWMENXZY56Y4ui
	 bT06MsrRUtH4qBp9rOhk7o34nGd5lFEzd7uWCriM=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org B05473858401
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1692364168; x=1692968968;
 h=content-transfer-encoding:to:subject:message-id:date:from
 :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc
 :subject:date:message-id:reply-to;
 bh=9z1CQGE9wD/+mBFjxyNAG8diI1tsqnMYCuAxuoOoV1w=;
 b=gCu7US/CpbRpVbYSOnaHeJwlkB5RM50u+zWCQtQn9UUZSTmXCAghEMiAvb/p8I2knM
 oQnwwY//n2LnoN56LJXic/SXBLvfdbm0LEzThqa15BiLrmX0PdSU2aHhpdlOx3WAZKv4
 O/Ikea/aQa4YA+XydnVIG3wBmoAnBF3s8IQLBnaQEsHx9oSL5mYbw0Ox3SR7cm0Er8vr
 ImAvWICS3hZAlKpJ1IAqfQgUx8PckEoVGuAPVPVlUlO+CWIwtHhThXuVzeP53UL8OUzB
 ITB39HgJsU27qAMPm9U6813/4CglqOtx1NdaCnyMwfjipAIfanUJ3hBfjNpQqlckfT32
 BQNg==
X-Gm-Message-State: AOJu0YztjBjVmTbEUQhfOQOusdqPJXYzFlFbWyhagCMxS+7R/kq0ueIg
 itUyaf3Why78ylMR+H83xBV9C78XrekV3lNeTnLH4bxmXRI=
X-Google-Smtp-Source: AGHT+IGhGig0WtogCNuL/l2v+0tqqhRljz+TIAHFmZ7M3ACII1wEYIuSFPbrEB6AVyCNLBzVUCaYziAo4bIbh+t+ioI=
X-Received: by 2002:a05:6808:1492:b0:3a1:f10c:f071 with SMTP id
 e18-20020a056808149200b003a1f10cf071mr1810634oiw.18.1692364167705; Fri, 18
 Aug 2023 06:09:27 -0700 (PDT)
MIME-Version: 1.0
References: <a0f1e420-ae48-49a3-9300-c56f1948ad9b DOT 8d485f54-9f47-42b0-bdcb-9635fbf663c3 DOT 6697971f-86bc-49dc-8072-c37095eed858 AT emailsignatures365 DOT codetwo DOT com>
 <a0f1e420-ae48-49a3-9300-c56f1948ad9b DOT 93e247b8-206a-49dd-b71c-9240681180cb DOT 7748cdc6-d053-4197-9372-3b4751ae3949 AT emailsignatures365 DOT codetwo DOT com>
 <a0f1e420-ae48-49a3-9300-c56f1948ad9b DOT e52b7f5f-5a09-4346-99f8-a6591191169c DOT 10af45d3-4cfc-48f7-a293-b6d9fa78cdd1 AT emailsignatures365 DOT codetwo DOT com>
 <AM5PR0502MB30752878C878948E660A73179210A AT AM5PR0502MB3075 DOT eurprd05 DOT prod DOT outlook DOT com>
 <ZNoAR4fBMXknsn5z AT calimero DOT vinschen DOT de>
 <CAKAoaQn47pu510onZDwh4baES-bhxtuSy3SxDCv7sXw5T94pzA AT mail DOT gmail DOT com>
 <CAKAoaQnvSZDD6mitFsdD==aOi0n9h3JSAEiJo8QXCRAf58H_Sw AT mail DOT gmail DOT com>
 <ZNqU5c5pMS2cQbsc AT calimero DOT vinschen DOT de>
 <CANH4o6OBo-vHUps6BbCn0X-w8Y49AADwB7PRfXPr+OH7GQ5TkQ AT mail DOT gmail DOT com>
 <ZN8vYctyNP0HRrbU AT calimero DOT vinschen DOT de>
In-Reply-To: <ZN8vYctyNP0HRrbU@calimero.vinschen.de>
Date: Fri, 18 Aug 2023 15:09:16 +0200
Message-ID: <CANH4o6P0XfmqjiiG+4eGmiz=4Vj8420Q6GSCz-PAwfnUUF-tzw@mail.gmail.com>
Subject: Cygwin pathconf() query filesystem kernel data? Re: How does Cygwin
 detect MSFT NFSv3 file system? Re: Weird (path) problems with cygwin test
 release 3.5.0-0.384.g9939aa7d0945.x86_64 ...
To: cygwin AT cygwin DOT com
X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,
 SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Martin Wege via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Martin Wege <martin DOT l DOT wege AT gmail DOT com>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 37ID9jRl021578

On Fri, Aug 18, 2023 at 10:44 AM Corinna Vinschen via Cygwin
<cygwin AT cygwin DOT com> wrote:
>
> On Aug 17 20:49, Martin Wege via Cygwin wrote:
> > On Mon, Aug 14, 2023 at 10:56 PM Corinna Vinschen via Cygwin
> > <cygwin AT cygwin DOT com> wrote:
> > > and the result is the same.  Note that Cygwin supports MSFT NFSv3 but
> > > not CITI NFSv4.1 internally.  No gurantee that Cygwin always does what
> > > is necessary for that other NFS.
> >
> > 1. How does Cygwin detect whether something is a MSFT NFSv3, or not?
> > Cygwin /bin/mount lists the CITI NFSv4.1 as 'nfs', so there *IS*
> > something which detects that?
>
> The filesystem name returned by NtQueryVolumeInformationFile is "NFS".
> If any other NFS returns the same filesystem name, it will be treated
> just like MSFT NFSv3.
>
> > 2. Are Cygwin soft link handing depend on MSFT NFSv3 or not, i.e. does
> > the Cygwin soft link code behave differently for MSFT NFSv3 file
> > systems?
>
> Yes.  NFS doesn't support symlink creation and symlink reading via
> the usual functions, because Windows symlinks are created as reparse
> points.  NFS doesn't support reparse points.  So the developers of
> the MSFT NFS client had to invent their own way to create and
> read NFS symlinks:
>
> https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/path.cc;hb=HEAD#l1719
>
> https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/path.cc;hb=HEAD#l2750
>
> > 3. Does Cygwin implement the pathconf() api?
>
> Yes.  Surprisingly, you can check this yourself by just calling the
> function and trying to compile your code.

Apologies, how do we say in German? "Ich sollte meine Frage konkretisieren:"

Does the Cygwin implementation of pathconf() support query data of the
underlying filesystem based on data from the kernel, as UNIX does? So
pathconf() returns different values for NTFS, ReFS, or Windows builtin
NFSv3?

I am asking, because as far as I know the Linux implementation is not
a syscall, and instead glibc guesses values based on builtin static
data, and whatever fstatfs() has to offer. Compared to that UNIX
(Solaris, AIX, HPUX, ...) have pathconf() as a syscall, and actually
ask the filesystem itself.

Thanks,
Martin

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple