linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "dai.ngo@oracle.com" <dai.ngo@oracle.com>,
	"Anna.Schumaker@netapp.com" <Anna.Schumaker@netapp.com>,
	"trondmy@kernel.org" <trondmy@kernel.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 2/2] NFSv4: Use the net namespace uniquifier if it is set
Date: Wed, 7 Oct 2020 22:28:11 +0000	[thread overview]
Message-ID: <d716cee24b7cc317b99beeefaa61e8db2a0e527a.camel@hammerspace.com> (raw)
In-Reply-To: <7eea5363-6f0c-0897-98e4-5a745130a1eb@oracle.com>

On Wed, 2020-10-07 at 15:02 -0700, Dai Ngo wrote:
> On 10/7/20 2:07 PM, trondmy@kernel.org wrote:
> > From: Trond Myklebust <trond.myklebust@hammerspace.com>
> > 
> > If a container sets a net namespace specific uniquifier, then use
> > that
> > in the setclientid/exchangeid process.
> > 
> > Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
> > ---
> >   fs/nfs/nfs4proc.c | 23 ++++++++++++++++++++---
> >   1 file changed, 20 insertions(+), 3 deletions(-)
> > 
> > diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
> > index 3a39887e0e6e..a1dd46e7440b 100644
> > --- a/fs/nfs/nfs4proc.c
> > +++ b/fs/nfs/nfs4proc.c
> > @@ -63,6 +63,7 @@
> >   #include "callback.h"
> >   #include "pnfs.h"
> >   #include "netns.h"
> > +#include "sysfs.h"
> >   #include "nfs4idmap.h"
> >   #include "nfs4session.h"
> >   #include "fscache.h"
> > @@ -6007,9 +6008,25 @@ static void nfs4_init_boot_verifier(const
> > struct nfs_client *clp,
> >   }
> >   
> >   static size_t
> > -nfs4_get_uniquifier(char *buf, size_t buflen)
> > +nfs4_get_uniquifier(struct nfs_client *clp, char *buf, size_t
> > buflen)
> >   {
> > +	struct nfs_net *nn = net_generic(clp->cl_net, nfs_net_id);
> > +	struct nfs_netns_client *nn_clp = nn->nfs_client;
> > +	const char *id;
> > +	size_t len;
> > +
> >   	buf[0] = '\0';
> > +
> > +	if (nn_clp) {
> > +		rcu_read_lock();
> > +		id = rcu_dereference(nn_clp->identifier);
> > +		if (id && *id != '\0')
> > +			len = strlcpy(buf, id, buflen);
> > +		rcu_read_unlock();
> > +		if (len)
> 
> I think 'len' can be uninitialized here.

Thanks. Yes, already noted and fixed in v2.

> 
> -Dai
> 
> > +			return len;
> > +	}
> > +
> >   	if (nfs4_client_id_uniquifier[0] != '\0')
> >   		return strlcpy(buf, nfs4_client_id_uniquifier, buflen);
> >   	return 0;
> > @@ -6034,7 +6051,7 @@ nfs4_init_nonuniform_client_string(struct
> > nfs_client *clp)
> >   		1;
> >   	rcu_read_unlock();
> >   
> > -	buflen = nfs4_get_uniquifier(buf, sizeof(buf));
> > +	buflen = nfs4_get_uniquifier(clp, buf, sizeof(buf));
> >   	if (buflen)
> >   		len += buflen + 1;
> >   
> > @@ -6081,7 +6098,7 @@ nfs4_init_uniform_client_string(struct
> > nfs_client *clp)
> >   	len = 10 + 10 + 1 + 10 + 1 +
> >   		strlen(clp->cl_rpcclient->cl_nodename) + 1;
> >   
> > -	buflen = nfs4_get_uniquifier(buf, sizeof(buf));
> > +	buflen = nfs4_get_uniquifier(clp, buf, sizeof(buf));
> >   	if (buflen)
> >   		len += buflen + 1;
> >   
-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



  reply	other threads:[~2020-10-07 22:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07 21:07 [PATCH 0/2] Give containers a unique client id trondmy
2020-10-07 21:07 ` [PATCH 1/2] NFSv4: Clean up initialisation of uniquified client id strings trondmy
2020-10-07 21:07   ` [PATCH 2/2] NFSv4: Use the net namespace uniquifier if it is set trondmy
2020-10-07 21:25     ` J. Bruce Fields
2020-10-07 21:34       ` Trond Myklebust
2020-10-07 21:45         ` bfields
2020-10-07 22:02     ` Dai Ngo
2020-10-07 22:28       ` Trond Myklebust [this message]
2020-10-07 22:40     ` kernel test robot

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=d716cee24b7cc317b99beeefaa61e8db2a0e527a.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=Anna.Schumaker@netapp.com \
    --cc=dai.ngo@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;
as well as URLs for NNTP newsgroup(s).