Date: Tue, 04 Jan 2022 23:38:28 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 260894] Nonexportable file systems are usable over NFSv4 Message-ID: <bug-260894-3630-oJkVjWZcHA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260894-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-260894-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260894 --- Comment #5 from Rick Macklem <rmacklem@FreeBSD.org> --- Take a look at usr.sbin/mountd/mountd.c, around line#3205-3264. If I read it correctly, a return from nmount(2) of EINVAL indicates "this is not a mount point". The loop then moves up a directory level and tries again. I have a hunch that what you did was export the underlying/parent file system and you were looking at "/mnt" in this parent file system. Short answer, try EPERM instead of EINVAL. Another issue is that nmount(2) is also used by mountd.c to delete exports, and that will fail too, if you have VFS_MOUNT() return a failure for that case. --> Might not matter if it has never been exported. --=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-3630-oJkVjWZcHA>