Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 02 Jan 2022 23:54:00 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 260894] Nonexportable file systems are usable over NFSv4
Message-ID:  <bug-260894-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260894

            Bug ID: 260894
           Summary: Nonexportable file systems are usable over NFSv4
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: asomers@FreeBSD.org

If I arrange for VFS_MOUNT to return EINVAL when MNT_EXPORT is set, add its
entry to /etc/fstab, and run "service mountd onereload", then the following
happens:

* mountd logs "can't export /mnt" to /var/log/messages.
* `showmount -e` does not list the file system.
* If I try to mount it from a client with NFS3, it always returns ESTALE.

However, I can still mount it from a client with NFS v4.2, and successfully
browse it.  This seems like a bug.  I would expect that mounting such a file
system with NFS v4.2 would work similarly to mounting a non-exported file
system: the mount would appear to succeed, but then `ls` would only show an
empty directory.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260894-227>