On Fri, Jan 12, 2024 at 2:24 AM Jeff Layton <jlayton@xxxxxxxxxx> wrote: > On Fri, 2024-01-12 at 01:44 +0100, Dan Shelton wrote: > > On Thu, 11 Jan 2024 at 23:53, Jeff Layton <jlayton@xxxxxxxxxx> wrote: > > > On Thu, 2024-01-11 at 22:27 +0100, Roland Mainz wrote: > > > > On Thu, Jan 11, 2024 at 4:55 PM Jeff Layton <jlayton@xxxxxxxxxx> 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: [snip] > > 2. No one is going to implement a giant set of code just so that SAMBA > > and NFSv4 can work. SAMBA has a builtin emulation so mandatory locking > > works between Windows clients, ignoring the Linux side and Linux > > advisory locking completely. > > > > Also, pretty much. With a general purpose OS like Linux, we try to avoid > this sort of emulation. We do have that for the share/deny locking that > happens during OPEN, but there was really no choice there since we > couldn't reasonably implement that in the VFS, and it was a required > part of the NFSv4 protocol. > > Mandatory locking is optional so we can just opt-out. How can I test for that in a NFSv4.1 client implementation ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz@xxxxxxxxxxx \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;)
