Received-SPF: pass (google.com: domain of linux-nfs+bounces-3564-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Message-ID: <34d9bb43-6fc4-4d8f-a29f-42c274b0ab89@cipixia.com>
Date: Wed, 5 Jun 2024 04:01:19 -0700
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: exports option "mountpoint" ignored in nfsv4, works in v3
To: Benjamin Coddington <bcodding@redhat.com>
Cc: linux-nfs@vger.kernel.org
References: <2c2f8e77-33c8-4836-b7e7-785938755e03@cipixia.com>
 <FF6EFB91-7045-42EB-B880-90F0B6933386@redhat.com>
Content-Language: en-US
From: Matt Kinni <matt@cipixia.com>
In-Reply-To: <FF6EFB91-7045-42EB-B880-90F0B6933386@redhat.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 6/3/24 05:56, Benjamin Coddington wrote:

> Its not that /srv/somemountpoint is always being exported, its that
> the v4 mount is mounting the root (/srv) and walking into
> /srv/somemountpoint.

But wouldn't this always be the case on an nfsv4 setup?  There is some
root folder that contains any child directories being exported
underneath it.

FWIW If I export the folder by itself and apply the mountpoint option to
it, eg. "/srv/somemountpoint *(rw,all_squash,fsid=0,mp)" as the only
export line, the mount command *does* indeed fail using -o vers=4.2,
however it doesn't fail with an error message - mount just hangs forever.

I feel like this is a regression compared against nfsv3 functionality
where "mountpoint" or "mp" can be applied to individual exports, and
generates an immediate error message for the client.  It seems with
nfsv4 the mp option only has an effect on the root export, and
accomplishes the deed by causing the client mount command to hang until
timeout