public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "William A. (Andy) Adamson" <androsadamson@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Benny Halevy <bhalevy@panasas.com>,
	linux-nfs@vger.kernel.org, pnfs@linux-nfs.org
Subject: Re: [pnfs] [PATCH 07/44] nfsd41: create_session check replay first
Date: Tue, 16 Jun 2009 21:15:32 -0400	[thread overview]
Message-ID: <89c397150906161815v6136e000t338f4fce10ceff23@mail.gmail.com> (raw)
In-Reply-To: <20090616204734.GE3045@fieldses.org>

On Tue, Jun 16, 2009 at 4:47 PM, J. Bruce Fields<bfields@fieldses.org> wrote:
> On Tue, Jun 16, 2009 at 04:19:32AM +0300, Benny Halevy wrote:
>> From: Andy Adamson <andros@netapp.com>
>>
>> Replay processing needs to preceed other error processing.
>
> Why?
>

Section 18.36.4. (CREATE_SESSION implementation section) states the
ordering of clientid confirmation processing as
1) client id record lookup
2) sequence id processing
3) client id confirmation

rpc cred processing is done in #3.

->Andy

> --b.
>
>>
>> Signed-off-by: Andy Adamson <andros@netapp.com>
>> Signed-off-by: Benny Halevy <bhalevy@panasas.com>
>> ---
>>  fs/nfsd/nfs4state.c |   12 ++++++------
>>  1 files changed, 6 insertions(+), 6 deletions(-)
>>
>> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
>> index bfc808b..5aef525 100644
>> --- a/fs/nfsd/nfs4state.c
>> +++ b/fs/nfsd/nfs4state.c
>> @@ -1378,12 +1378,6 @@ nfsd4_create_session(struct svc_rqst *rqstp,
>>               }
>>               conf->cl_slot.sl_seqid++;
>>       } else if (unconf) {
>> -             if (!same_creds(&unconf->cl_cred, &rqstp->rq_cred) ||
>> -                 (ip_addr != unconf->cl_addr)) {
>> -                     status = nfserr_clid_inuse;
>> -                     goto out_cache;
>> -             }
>> -
>>               slot = &unconf->cl_slot;
>>               status = check_slot_seqid(cr_ses->seqid, slot->sl_seqid, 0);
>>               if (status) {
>> @@ -1392,6 +1386,12 @@ nfsd4_create_session(struct svc_rqst *rqstp,
>>                       goto out;
>>               }
>>
>> +             if (!same_creds(&unconf->cl_cred, &rqstp->rq_cred) ||
>> +                 (ip_addr != unconf->cl_addr)) {
>> +                     status = nfserr_clid_inuse;
>> +                     goto out_cache;
>> +             }
>> +
>>               slot->sl_seqid++; /* from 0 to 1 */
>>               move_to_confirmed(unconf);
>>
>> --
>> 1.6.3
>>
> _______________________________________________
> pNFS mailing list
> pNFS@linux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
>

  parent reply	other threads:[~2009-06-17  1:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16  1:19 [PATCH 07/44] nfsd41: create_session check replay first Benny Halevy
2009-06-16 20:47 ` J. Bruce Fields
2009-06-16 21:16   ` J. Bruce Fields
2009-06-17  1:22     ` [pnfs] " William A. (Andy) Adamson
2009-06-17  1:15   ` William A. (Andy) Adamson [this message]
     [not found]     ` <89c397150906161815v6136e000t338f4fce10ceff23-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-17  1:25       ` J. Bruce Fields
2009-06-17  1:39         ` William A. (Andy) Adamson

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=89c397150906161815v6136e000t338f4fce10ceff23@mail.gmail.com \
    --to=androsadamson@gmail.com \
    --cc=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