DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 5327e6Ss2671936
Authentication-Results:	delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 5327e6Ss2671936
Authentication-Results:	delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=KPuaUct4
X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org A9F40384CB87
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1743579605;
	bh=qiW5ZUyA6HkPpbpyS925ToJ0D/WLGYuz4ed4z5r2i7U=;
	h=Date:Subject:To:List-Id:List-Unsubscribe:List-Archive:List-Post:
	List-Help:List-Subscribe:From:Reply-To:From;
	b=KPuaUct4MAuO/ZDW62vhBGi1LduagRjGVyjyLJRSBWykfEqXivQNb53lB91Y1bR4x
	neP9yq2hJWaYspTKhxgIF+aCjjypN7jiRUu9VQdmfCLHwIunwAEyHK13m4djdhk7SY
	qZj0EYOVbtbBZb4h+Qq2PrFPAg1vBOpIyOOGFhbs=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org D6BD33857B8C
ARC-Filter:	OpenARC Filter v1.0.0 sourceware.org D6BD33857B8C
ARC-Seal:	i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1743579537; cv=none;
	b=s5BneYeVaKXvAAFqzD+X8QgCdbGfs9m1uItqVv/9UH4IhGAyC4mLK2ieOa6RqVKphilodtAT6BbYIBSHU3/b31aEmBIls71Pe7QSh1B2pSVf94dwltqX9P+tudrlkmYWXV3ce2a3kg1zHaPKMOlkAC9IYUI3rUU0CBMSPSoH/+k=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1743579537; c=relaxed/simple;
	bh=tsVPUvG2/GdQ9AcrxFv32MKqOEdtCBdF68dSyJLVSdU=;
	h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To;
	b=nCAxUVWvAQmviqjPoALwDiSJh9sQP33j85di9O5ZQ5HWCN71Qz4vZ/I8cN+IdSIXxmXc+nGAbxND1RF0DRbWVD6NKDI06xmGykjE1InHcwZfA2eTyGtxkMHyvVSk3kDCBpOHhTCtO9moEvjv8rid34D9i62c3OnyGsAPVKScka4=
ARC-Authentication-Results:	i=1; server2.sourceware.org
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org D6BD33857B8C
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20230601; t=1743579535; x=1744184335;
	h=content-transfer-encoding:to:subject:message-id:date:from
	:mime-version:x-gm-message-state:from:to:cc:subject:date:message-id
	:reply-to;
	bh=ttyklZcrHBDTrL64B3C49kxV9bKyDnhLIrMYGjsPF1Y=;
	b=PyaNyrmzy3afHehaZHTIom/fp2V3BvjEDRlUXInlRalULXI4q5jrJIKy+2gy0JWZE1
	wjbUGV+bBNDapBuH30rmLR5I2+W+nnFARQAJJBusPoEV/dC4mW34gNx00pD+3/z8NOPg
	A82bQuyaY1rpWoJj0Z9PKw4NbCrODYC1iS5YDqbTU5r5paAfPJNAssnFPUOJjDq/mGa2
	5ACchkR6Uppf1qtlmsGlW78F5FZdJUqoJiKQ1gHMJzH7nA/HobQtZFhAtr5oRyvnNKLY
	2D5/Fsd95wSGeZlPrf3LhsLmrDtMnepd8HSk4l9Cqnvl/o7BrfWRsdlOQWadLD0b3ju1
	Ncfw==
X-Gm-Message-State:	AOJu0YxBgcyjgiAm40a4plBcNdy68/SG8MnBZEZGXDU/C7hhJgCfzYJK
	VXE1Y6ghumbdy3suk5Yt4UeA4fOYC62Av9oPJE7qzIXntCzF3hjCQ3QT1AN9CrpCKLkyPHGaG2s
	TCdGYaH4Q9PkQyWU3/M3eDw2VYeXxlUGQ
X-Gm-Gg:	ASbGncv/naI3reRxUh61j14H8RXQo9jvfoo0MKQ4X8MFt0D7RoILRc2VJh6szgQ9rnp
	c/h8hKqV04sf29dWWVCaCPu4q19dBl7QXucbBUffVjvI43s66/z/y1YTx/J0QayE4n5U5xx2+wW
	IqbMqlf1NQB28toWDS+/ytlZgibMc=
X-Google-Smtp-Source:	AGHT+IGjp6sINyTN++SBue9ilSOgAKuL4mMRqwFxWpLJLRmHIcaIVt8N/dBE8RvMEl91pq+f3bayd9CEsTtXv+E2tSs=
X-Received:	by 2002:a17:90a:d647:b0:2ea:83a0:47a5 with SMTP id
	98e67ed59e1d1-30531f79f9amr24625604a91.4.1743579535381; Wed, 02 Apr 2025
	00:38:55 -0700 (PDT)
MIME-Version:	1.0
Date:	Wed, 2 Apr 2025 09:38:00 +0200
X-Gm-Features:	AQ5f1Jo87Prx5FXVtStY0eQ69hRCtHQJUHA6kLehCWoZudW-mHcbJlUOmib06UA
Message-ID:	<CALXu0UfWK6MMe9CFBD547YYyqke=fNKoK3-TvGeJmaVo=HqiwA@mail.gmail.com>
Subject:	Windows Remote Driver Identification Re: Cygwin wishlist for NFSv4.2
	driver? Re: [Ms-nfs41-client-devel] ANN: NFSv4.2/NFSv4.1 filesystem
	client
	Windows driver binaries for Windows 10/11+WindowsServer 2019/2022 for
	testing, 2025-03-31 ...
To:	cygwin AT cygwin DOT com, Ms-nfs41-client-devel AT lists DOT sourceforge DOT net
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
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:	Cedric Blancher via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Cedric Blancher <cedric DOT blancher AT gmail DOT com>
Sender:	"Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 5327e6Ss2671936

On Tue, 1 Apr 2025 at 13:54, Corinna Vinschen via Cygwin
<cygwin AT cygwin DOT com> wrote:
>
> On Apr  1 12:27, Cedric Blancher via Cygwin wrote:
> > On Tue, 1 Apr 2025 at 09:46, Cedric Blancher <cedric DOT blancher AT gmail DOT com> wrote:
> > >
> > > Good morning!
> > >
> > > For your consideration - we need FEEDBACK, please!
> > >
> > > New is:
> > > - 2nd Spring-Release (🐝)
> > > - Improved Windows Extended Attribute (EA) support
> > > - Sparse file support (https://en.wikipedia.org/wiki/Sparse_file) for
> > > HPC environments
> > > - Symlink conversion, to make Windows symlinks exchangeable with other
> > > NFS clients on other platforms
> > > - Windows Server 2019 NFSv4.1 nfsd, Windows Server 2022 NFSv4.1 nfsd,
> > > Solaris 11.4 NFSv4.1 nfsd and Illumos NFSv4.2 nfsd support
> > > - Better WSL (Windows Services for Linux) support
> > > - MSYS2 support
> > > - Windows Storage32 API support, required for using MSI installer
> > > files on NFS mounts
> > > - Support for languages with wide characters (Japanese, Chinese,
> > > Hindi, French...) in nfs://-URLs
> > > - Display mount points with wide-characters in nfs_mount.exe correctly
> >
> > New thread:
> > Does Cygwin have any requests, or ideas, what could be improved in the
> > ms-nfs41-client NFSv4.2 driver for Windows? New features?
>
> No, but if we want to *better* support this driver, we need either a
> patch (preferred) or at least info how to distinguish in
> fs_info::update(*) between the MSFT driver and the NFSv4.2 driver.

That is actually easy: Roland implemented support for
FileRemoteProtocolInformation in
https://github.com/kofemann/ms-nfs41-client/commit/e9f72b61494bebd9e26fefec2659a4511a05b0fd
 , and the FILE_REMOTE_PROTOCOL_INFORMATION->Protocol field can be
used to identify the type of driver.

Examples:
Windows NFSv3 driver uses WNNC_NET_MS_NFS,
OpenAFS uses WNNC_NET_OPENAFS, ms-nfs41-client uses
WNNC_NET_RDR2SAMPLE, and OpenText NFS also uses WNNC_NET_RDR2SAMPLE.

Plan for ms-nfs42-client is to obtain an own WNNC_NET_MSNFS42CLIENT
tag, and also tags for DOKANY.

In your case all workarounds for the Windows NFSv3 driver would be
enableds just by doing a FileRemoteProtocolInformation query, #define
IS_MS_NFSV3_DRIVER(rpi) (rpi->Protocol == WNNC_NET_MS_NFS), and put
if(IS_MS_NFSV3_DRIVER(&saved_rpi)) { ... } in places where needed.

Same test can be done for SMB, OpenAFS, Windows DAV driver,
Windows/WSL 9P, Terminal server.

There is also https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/fltuserstructures/ne-fltuserstructures-_flt_filesystem_type
but I do not know in which context that is used. Maybe you or Roland
know that.

Ced
--
Cedric Blancher <cedric DOT blancher AT gmail DOT com>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur

-- 
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

- Raw text -