This got missed when the flag was added. Document it properly. Signed-off-by: Jeff Layton --- Documentation/filesystems/nfs/exporting.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Documentation/filesystems/nfs/exporting.rst b/Documentation/filesystems/nfs/exporting.rst index de64d2d002a204c5460980c898d4ec41fd43d47a..0583a0516b1e3a3e6a10af95ff88506cf02f7df4 100644 --- a/Documentation/filesystems/nfs/exporting.rst +++ b/Documentation/filesystems/nfs/exporting.rst @@ -238,3 +238,9 @@ following flags are defined: all of an inode's dirty data on last close. Exports that behave this way should set EXPORT_OP_FLUSH_ON_CLOSE so that NFSD knows to skip waiting for writeback when closing such files. + + EXPORT_OP_NOLOCKS - Disable file locking on this filesystem. Some + filesystems cannot properly support file locking as implemented by + nfsd. A case in point is reexport of NFS itself, which can't be done + safely without coordinating the grace period handling. Other clustered + and networked filesystems can be problematic here as well. -- 2.52.0