Received-SPF: pass (google.com: domain of linux-nfs+bounces-1049-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Precedence: bulk
MIME-Version: 1.0
References: <CAKAoaQniGNGuPm5CTTs3oJRuCH40HTt6K91nCAPRnt0tECxkBA@mail.gmail.com>
 <bce828afb68c973d684b3e179cf8d6ce39c8b9c3.camel@kernel.org>
 <39adc7fc114c6f8ea38fe7c846c322dab5fac907.camel@kernel.org> <CAKAoaQkdY-NOgWoVKN+oitTSFbmfC7fixoxDfXR0SF-6EJrEOw@mail.gmail.com>
In-Reply-To: <CAKAoaQkdY-NOgWoVKN+oitTSFbmfC7fixoxDfXR0SF-6EJrEOw@mail.gmail.com>
From: Dan Shelton <dan.f.shelton@gmail.com>
Date: Fri, 12 Jan 2024 01:20:02 +0100
Message-ID: <CAAvCNcCpHHCGfmRXN2n35xhzvL-te1iaG+=56H32E89GvCJQeQ@mail.gmail.com>
Subject: Re: NFSv4.1 mandatory locks working in Linux nfsd ?
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, 11 Jan 2024 at 22:28, Roland Mainz <roland.mainz@nrubsig.org> wrote=
:
>
> On Thu, Jan 11, 2024 at 4:55=E2=80=AFPM Jeff Layton <jlayton@kernel.org> =
wrote:
> > On Thu, 2024-01-11 at 10:54 -0500, Jeff Layton wrote:
> > > On Sun, 2023-12-24 at 18:29 +0100, Roland Mainz wrote:
> > > > Are there any known issues with NFSv4.1 mandatory locking nfsd code=
 in
> > > > the Linux 5.10.0-22-rt-amd64 kernel (technically the Debian Bullsey=
e
> > > > RT kernel) ? Is there any kernel or NFS test suite module which cov=
ers
> > > > NFSv4.1 client mandatory locking ?
> > >
> > > Linux doesn't support mandatory locking at all since 2021 [1]. The Li=
nux
> > > NFS client and server therefore do not support v4.1 mandatory locking=
.
> >
> > Forgot the footnote!
> >
> > [1]: https://patchwork.kernel.org/project/linux-fsdevel/patch/202108201=
14046.69282-1-jlayton@kernel.org/
>
> OK, this is pretty bad in terms of interoperability.... ;-(
>
> What should a Windows NFSv4 client (Hummingbird, OpenText, Exceed,
> ms-nfs41-client, ...) do in this case ?
> It basically means that locking for these clients will fail if the
> server does not support it... ;-(

The Windows nfsd supports NFSv4 with mandatory locking. Or use SAMBA
like everyone else.

Honestly, while your msnfs41client for Windows is impressive, the
NFSv4 protocol is fighting a losing battle against SAMBA on every
other front than Linux. Even the HPC market is evaporating for NFS
since the day M$ came up with SMB DIRECT, as SMB over RDMA.

Dan
--=20
Dan Shelton - Cluster Specialist Win/Lin/Bsd