public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Benny Halevy <bhalevy@panasas.com>
Cc: pnfs@linux-nfs.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 33/44] nfsd41: Remove ip address collision detection case per review comment
Date: Thu, 18 Jun 2009 19:36:44 -0400	[thread overview]
Message-ID: <20090618233644.GA15962@fieldses.org> (raw)
In-Reply-To: <1245115247-7890-1-git-send-email-bhalevy@panasas.com>

On Tue, Jun 16, 2009 at 04:20:47AM +0300, Benny Halevy wrote:
> From: Mike Sager <sager@netapp.com>
> 
> Verified that cthon and pynfs exchange id tests pass (except for the
> two expected fails: EID8 and EID50)

Thanks, applied.  Though exchange_id still isn't right: for example,
we're expiring the client in the conf && !same_verf case without
checking the principal.

If someone could take an hour or two, go through the 18.35.4 *very*
carefully, and check all of this, it would be appreciated.

--b.

> 
> Signed-off-by: Mike Sager <sager@netapp.com>
> Signed-off-by: Benny Halevy <bhalevy@panasas.com>
> ---
>  fs/nfsd/nfs4state.c |   18 ++++++------------
>  1 files changed, 6 insertions(+), 12 deletions(-)
> 
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index c91b333..8ac5630 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -1158,12 +1158,6 @@ nfsd4_exchange_id(struct svc_rqst *rqstp,
>  			expire_client(conf);
>  			goto out_new;
>  		}
> -		if (ip_addr != conf->cl_addr &&
> -		    !(exid->flags & EXCHGID4_FLAG_UPD_CONFIRMED_REC_A)) {
> -			/* Client collision. 18.35.4 case 3 */
> -			status = nfserr_clid_inuse;
> -			goto out;
> -		}
>  		/*
>  		 * Set bit when the owner id and verifier map to an already
>  		 * confirmed client id (18.35.3).
> @@ -1177,12 +1171,12 @@ nfsd4_exchange_id(struct svc_rqst *rqstp,
>  		copy_verf(conf, &verf);
>  		new = conf;
>  		goto out_copy;
> -	} else {
> -		/* 18.35.4 case 7 */
> -		if (exid->flags & EXCHGID4_FLAG_UPD_CONFIRMED_REC_A) {
> -			status = nfserr_noent;
> -			goto out;
> -		}
> +	}
> +
> +	/* 18.35.4 case 7 */
> +	if (exid->flags & EXCHGID4_FLAG_UPD_CONFIRMED_REC_A) {
> +		status = nfserr_noent;
> +		goto out;
>  	}
>  
>  	unconf  = find_unconfirmed_client_by_str(dname, strhashval, true);
> -- 
> 1.6.3
> 

      reply	other threads:[~2009-06-18 23:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16  1:20 [PATCH 33/44] nfsd41: Remove ip address collision detection case per review comment Benny Halevy
2009-06-18 23:36 ` J. Bruce Fields [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=20090618233644.GA15962@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bhalevy@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=pnfs@linux-nfs.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