All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Wed, 09 Feb 2022 12:24:59 +1100	[thread overview]
Message-ID: <164436989902.27779.4490909869062483924@noble.neil.brown.name> (raw)
In-Reply-To: <06e2a692e587d1ffcccd14d465136df228149e4c.camel@hammerspace.com>

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

  reply	other threads:[~2022-02-09  2:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-05 15:03 v4 clientid uniquifiers in containers/namespaces Benjamin Coddington
2022-02-05 18:24 ` Trond Myklebust
2022-02-05 19:50   ` Benjamin Coddington
2022-02-07 14:05     ` Benjamin Coddington
2022-02-07 15:49       ` Chuck Lever III
2022-02-07 19:38         ` Trond Myklebust
2022-02-07 23:59           ` Chuck Lever III
2022-02-08 11:32             ` Benjamin Coddington
2022-02-08 13:45               ` Trond Myklebust
2022-02-08 14:29                 ` Benjamin Coddington
2022-02-08 14:42                   ` Chuck Lever III
2022-02-08 15:23                     ` Benjamin Coddington
2022-02-08 15:43                       ` Trond Myklebust
2022-02-08 15:47                         ` Trond Myklebust
2022-02-08 16:18                           ` Benjamin Coddington
2022-02-08 16:47               ` Trond Myklebust
2022-02-08 17:45                 ` Benjamin Coddington
2022-02-08  1:59 ` NeilBrown
2022-02-08 11:52   ` Benjamin Coddington
2022-02-08 20:56     ` NeilBrown
2022-02-08 23:34       ` Trond Myklebust
2022-02-09  1:24         ` NeilBrown [this message]
2022-02-15 16:57         ` Benjamin Coddington

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=164436989902.27779.4490909869062483924@noble.neil.brown.name \
    --to=neilb@suse.de \
    --cc=bcodding@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@hammerspace.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.