From: "Benjamin Coddington" <bcodding@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: "Trond Myklebust" <trondmy@hammerspace.com>,
steved@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [nfs-utils PATCH] nfs4id: a tool to create and persist nfs4 client uniquifiers
Date: Mon, 14 Feb 2022 06:34:49 -0500 [thread overview]
Message-ID: <2B965E03-552B-4A5A-85E7-53E65729198D@redhat.com> (raw)
In-Reply-To: <164479465866.27779.3680126986096452561@noble.neil.brown.name>
On 13 Feb 2022, at 18:24, NeilBrown wrote:
> Document the requirement and make it "someone elses problem".
> Your kernel patch to provide a random default mean a lack of
> configuration will only hurt the container which lacks it - which nicely
> localises the problem.
I thought of another approach which was to have either mount.nfs or the
kernel emit a warning if a client is not uniquified.
Ben
prev parent reply other threads:[~2022-02-14 11:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 12:56 [nfs-utils PATCH] nfs4id: a tool to create and persist nfs4 client uniquifiers Benjamin Coddington
2022-02-04 15:17 ` Chuck Lever III
2022-02-04 15:49 ` Benjamin Coddington
2022-02-04 18:45 ` Chuck Lever III
2022-02-04 19:44 ` Benjamin Coddington
2022-02-05 17:35 ` Chuck Lever III
2022-02-08 3:14 ` NeilBrown
2022-02-08 11:43 ` Benjamin Coddington
2022-02-08 16:04 ` Steve Dickson
2022-02-08 16:21 ` Chuck Lever III
2022-02-08 19:29 ` Steve Dickson
2022-02-08 21:18 ` Chuck Lever III
2022-02-08 22:39 ` Steve Dickson
2022-02-10 13:28 ` Benjamin Coddington
2022-02-10 15:21 ` Chuck Lever III
2022-02-10 15:47 ` Benjamin Coddington
2022-02-10 16:25 ` Chuck Lever III
2022-02-10 16:41 ` Benjamin Coddington
2022-02-10 17:11 ` Steve Dickson
2022-02-08 16:22 ` Benjamin Coddington
2022-02-08 19:52 ` Steve Dickson
2022-02-08 20:00 ` Benjamin Coddington
2022-02-08 22:30 ` Steve Dickson
2022-02-09 13:55 ` Benjamin Coddington
2022-02-09 15:23 ` Steve Dickson
2022-02-09 21:21 ` NeilBrown
2022-02-09 21:45 ` Trond Myklebust
2022-02-09 23:58 ` NeilBrown
2022-02-10 12:25 ` Benjamin Coddington
2022-02-10 22:54 ` NeilBrown
2022-02-11 13:35 ` Benjamin Coddington
2022-02-13 23:24 ` NeilBrown
2022-02-14 11:34 ` Benjamin Coddington [this message]
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=2B965E03-552B-4A5A-85E7-53E65729198D@redhat.com \
--to=bcodding@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=steved@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox