From: trondmy@kernel.org
To: Anna Schumaker <Anna.Schumaker@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v2 0/2] Give containers a unique client id
Date: Wed, 7 Oct 2020 18:24:16 -0400 [thread overview]
Message-ID: <20201007222418.604115-1-trondmy@kernel.org> (raw)
From: Trond Myklebust <trond.myklebust@hammerspace.com>
This series adds the missing patches to allow a container to set a
unique client id using /sys/fs/nfs/net/nfs_client/identifier, and
have NFS use that for any new NFS mounts that are initiated by that
container.
--
v2: Fix a variable initialisation in nfs4_get_uniquifier
Switch to using preferred strscpy()
Trond Myklebust (2):
NFSv4: Clean up initialisation of uniquified client id strings
NFSv4: Use the net namespace uniquifier if it is set
fs/nfs/nfs4proc.c | 88 +++++++++++++++++++++++++----------------------
1 file changed, 47 insertions(+), 41 deletions(-)
--
2.26.2
next reply other threads:[~2020-10-07 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 22:24 trondmy [this message]
2020-10-07 22:24 ` [PATCH v2 1/2] NFSv4: Clean up initialisation of uniquified client id strings trondmy
2020-10-07 22:24 ` [PATCH v2 2/2] NFSv4: Use the net namespace uniquifier if it is set trondmy
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=20201007222418.604115-1-trondmy@kernel.org \
--to=trondmy@kernel.org \
--cc=Anna.Schumaker@netapp.com \
--cc=linux-nfs@vger.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;
as well as URLs for NNTP newsgroup(s).