linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "bfields@fieldses.org" <bfields@fieldses.org>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "trondmy@kernel.org" <trondmy@kernel.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"Anna.Schumaker@netapp.com" <Anna.Schumaker@netapp.com>
Subject: Re: [PATCH 2/2] NFSv4: Use the net namespace uniquifier if it is set
Date: Wed, 7 Oct 2020 17:45:33 -0400	[thread overview]
Message-ID: <20201007214533.GJ23452@fieldses.org> (raw)
In-Reply-To: <9b44b51fd7f65274a76b167b9c0b3231a7d50f99.camel@hammerspace.com>

On Wed, Oct 07, 2020 at 09:34:17PM +0000, Trond Myklebust wrote:
> On Wed, 2020-10-07 at 17:25 -0400, J. Bruce Fields wrote:
> > On Wed, Oct 07, 2020 at 05:07:20PM -0400, trondmy@kernel.org wrote:
> > > From: Trond Myklebust <trond.myklebust@hammerspace.com>
> > > 
> > > If a container sets a net namespace specific uniquifier,
> > 
> > What you're actually checking is if nn->nfs_client != NULL, and
> > that's
> > pretty much always true.  (The only time it's NULL is an allocation
> > failure in some initialization code, I think.)
> > 
> > > +	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) {
> > 
> > Are you sure you don't mean
> > 
> > 	if (nn_clp->identifier)
> > 
> > ?
> > 
> > I think that's how you tell if someone's set it.
> 
> We're not holding the rcu_read_lock() here, so there is no point in
> dereferencing the identifier pointer. That would cause a toctou race...

Oh, right:

> > > +		rcu_read_lock();
> > > +		id = rcu_dereference(nn_clp->identifier);
> > > +		if (id && *id != '\0')

My bad, I saw the first check and missed that one somehow.

> > > +			len = strlcpy(buf, id, buflen);
> > > +		rcu_read_unlock();
> > > +		if (len)
> > > +			return len;
> 
> Oops. However I do need to ensure that 'len' is always initialised
> here.

OK.--b.

> 
> > > +	}
> > > +
> > >  	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;
> > >  
> > > -- 
> > > 2.26.2
> -- 
> Trond Myklebust
> Linux NFS client maintainer, Hammerspace
> trond.myklebust@hammerspace.com
> 
> 

  reply	other threads:[~2020-10-07 21:45 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 [this message]
2020-10-07 22:02     ` Dai Ngo
2020-10-07 22:28       ` Trond Myklebust
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=20201007214533.GJ23452@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Anna.Schumaker@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@hammerspace.com \
    --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).