Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
From:   "NeilBrown" <neilb@suse.de>
To:     "Trond Myklebust" <trondmy@hammerspace.com>
Cc:     "bcodding@redhat.com" <bcodding@redhat.com>,
        "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: v4 clientid uniquifiers in containers/namespaces
In-reply-to: <06e2a692e587d1ffcccd14d465136df228149e4c.camel@hammerspace.com>
References: <6CEC5101-0512-4082-81F8-BDFEC5B6DF3A@redhat.com>,
 <164428557862.27779.17375354328525752842@noble.neil.brown.name>,
 <A677D8A9-FD0B-43E5-82D6-E660CCB8B185@redhat.com>,
 <164435376000.27779.4059629372785561121@noble.neil.brown.name>,
 <06e2a692e587d1ffcccd14d465136df228149e4c.camel@hammerspace.com>
Date:   Wed, 09 Feb 2022 12:24:59 +1100
Message-id: <164436989902.27779.4490909869062483924@noble.neil.brown.name>
Precedence: bulk

On Wed, 09 Feb 2022, Trond Myklebust wrote:
> On Wed, 2022-02-09 at 07:56 +1100, NeilBrown wrote:
> > 
> > So I still STRONGLY think that the identity should be set by
> > mount.nfs
> > reading (and writing) some file in /etc or /etc/netnfs/NAME, and I
> > weakly think that the file should be in /etc/nfs.conf.d/ so that the
> > reading is automagic.
> > 
> 
> No. It's not a per-mount setting, so it has no business being in the
> mount protocol.

I agree that it is not different for different mounts, but every mount
needs it, and without any mounts it is not needed.

Much like statd really, which is started by mount.nfs when it is
determined that it is needed, but not running.

NeilBrown