From: Christoph Hellwig <hch@lst.de>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
Trond Myklebust <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/2] NFS: add a clientid mount option
Date: Mon, 14 Jul 2025 15:31:35 +0200 [thread overview]
Message-ID: <20250714133135.GB10090@lst.de> (raw)
In-Reply-To: <cf337014-f8a6-44d6-8760-61663fef576d@oracle.com>
On Mon, Jul 14, 2025 at 09:24:20AM -0400, Chuck Lever wrote:
> On 7/14/25 2:30 AM, Christoph Hellwig wrote:
> > Add a mount option to set a clientid, similarly to how it can be
> > configured through the per-netfs sysfs file. This allows for easy
> > testing of behavior that relies on the client ID likes locks or
> > delegations with having to resort to separate VMs or containers.
>
> The problem with approaches like this is that it becomes difficult
> to manage multiple mounts of the same server. Each of those mounts
> really cannot have a different clientid.
Having different clientids for multiple mounts from the same server
is the purpose and only reason for this option.
> For testing, why can't you use the per-container clientid setting?
Because having to create a container is a lot of effort when all
that is needed is just a mount with a different clientid.
next prev parent reply other threads:[~2025-07-14 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 6:30 add a clientid mount option Christoph Hellwig
2025-07-14 6:30 ` [PATCH 1/2] NFS: pass struct nfs_client_initdata to nfs4_set_client Christoph Hellwig
2025-07-14 15:51 ` Trond Myklebust
2025-07-14 6:30 ` [PATCH 2/2] NFS: add a clientid mount option Christoph Hellwig
2025-07-14 13:24 ` Chuck Lever
2025-07-14 13:31 ` Christoph Hellwig [this message]
2025-07-14 14:47 ` Chuck Lever
2025-07-14 15:49 ` Trond Myklebust
2025-07-15 5:31 ` Christoph Hellwig
2025-07-15 5:30 ` Christoph Hellwig
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=20250714133135.GB10090@lst.de \
--to=hch@lst.de \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@kernel.org \
/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