linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Mi Jinlong <mijinlong@cn.fujitsu.com>
Cc: NFS <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 10/17] CLNT: test resues slot ID
Date: Thu, 3 Mar 2011 09:51:09 -0500	[thread overview]
Message-ID: <20110303145109.GA11402@fieldses.org> (raw)
In-Reply-To: <4D6F5B4E.7000903@cn.fujitsu.com>

On Thu, Mar 03, 2011 at 05:11:42PM +0800, Mi Jinlong wrote:
> 
> 
> J. Bruce Fields:
> > On Wed, Mar 02, 2011 at 02:33:09PM +0800, Mi Jinlong wrote:
> >> Signed-off-by: Mi Jinlong <mijinlong@cn.fujitsu.com>
> >> ---
> >>  nfs4.1/server41tests/st_sequence.py |   18 ++++++++++++++++++
> >>  1 files changed, 18 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/nfs4.1/server41tests/st_sequence.py b/nfs4.1/server41tests/st_sequence.py
> >> index 4ea5cab..391fc45 100644
> >> --- a/nfs4.1/server41tests/st_sequence.py
> >> +++ b/nfs4.1/server41tests/st_sequence.py
> >> @@ -363,3 +363,21 @@ def testBadSequenceidAtSlot(t, env):
> >>  
> >>      res = c.c.compound([op.sequence(sid, nfs4lib.dec_u32(seqid), 2, 3, True)])
> >>      check(res, NFS4ERR_SEQ_MISORDERED)
> >> +
> >> +def testReuseSlotID(t, env):
> >> +    """
> >> +
> >> +    FLAGS: sequence all
> >> +    CODE: SEQ14
> >> +    """
> > 
> > Missing description?
> 
>   Sorry! I will add it at next version.
> 
> > 
> >> +    c = env.c1.new_client(env.testname(t))
> >> +    # CREATE_SESSION
> >> +    sess1 = c.create_session()
> >> +
> >> +    sid = sess1.sessionid 
> >> +    res = c.c.compound([op.sequence(sid, 1, 2, 3, True), op.putrootfh()])
> >> +    check(res)
> >> +
> >> +    res = c.c.compound([op.sequence(sid, 1, 2, 3, True)])
> >> +    # should we also check the ERROR of NFS4ERR_SEQ_FALSE_RETRY ??
> > 
> > As I understand it, the server isn't required to recognize false
> > retries, so I don't think we can check for that.
> > 
> > The only useful thing to check for, I think, is just to send the same
> > request twice and make sure the requests match.
> > 
> > Actually, best would be to do this with a non-idempotent operation.  For
> > example, send SEQ+RENAME twice and make sure that both renames succeed.
> > (Whereas if the server reply cache is broken and the server attempts to
> > rename the file again, the second rename will fail with NOENT.)
> 
>   Yes, thanks for you advice.
>   I will send a new patch tomorrow.

OK, thanks.  The patches I didn't comment on look mostly fine to me;
I'll push them out to my git tree as I apply them.

--b.

  reply	other threads:[~2011-03-03 14:51 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02  6:23 [PATCH 00/17] add some test case for pynfs41 Mi Jinlong
2011-03-02  6:26 ` [PATCH 01/17] CLNT: check NFS4ERR_NOT_ONLY_OP for CREATE_SESSION Mi Jinlong
2011-03-03  5:57   ` J. Bruce Fields
2011-03-02  6:27 ` [PATCH 02/17] CLNT: test lease period of unconfirmed record Mi Jinlong
2011-03-02  6:28   ` [PATCH 03/17] CLNT: check the csr_sequence at CREATE_SESSION Mi Jinlong
2011-03-03  6:02   ` [PATCH 02/17] CLNT: test lease period of unconfirmed record J. Bruce Fields
2011-03-03  9:07     ` Mi Jinlong
2011-03-09  1:29       ` J. Bruce Fields
2011-03-09  1:43         ` Mi Jinlong
2011-03-02  6:29 ` [PATCH 04/17] CLNT: test with ca_maxresponsesize is too small Mi Jinlong
2011-03-02  6:29 ` [PATCH 05/17] CLNT: test reply too big Mi Jinlong
2011-03-02  6:30 ` [PATCH 06/17] CLNT: test reply too big to cache Mi Jinlong
2011-03-02  6:31 ` [PATCH 07/17] CLNT: test operation not in session Mi Jinlong
2011-03-02  6:31 ` [PATCH 08/17] CLNT: test the sessionid, slotid and sequenceid for SEQUENCE Mi Jinlong
2011-03-02  6:32 ` [PATCH 09/17] CLNT: test Bad Sequenceid At Slot Mi Jinlong
2011-03-02  6:33 ` [PATCH 10/17] CLNT: test resues slot ID Mi Jinlong
2011-03-03  6:14   ` J. Bruce Fields
2011-03-03  9:11     ` Mi Jinlong
2011-03-03 14:51       ` J. Bruce Fields [this message]
2011-03-04  9:06       ` Mi Jinlong
2011-03-14 18:41         ` J. Bruce Fields
2011-03-14 19:24           ` J. Bruce Fields
2011-03-15  2:47             ` Mi Jinlong
2011-03-17 22:52               ` J. Bruce Fields
2011-03-22  9:44                 ` Mi Jinlong
2011-03-22 21:48                   ` J. Bruce Fields
2011-03-23  9:41                     ` Mi Jinlong
2011-03-02  6:33 ` [PATCH 11/17] CLNT: DESTROY_SESSION not the fianl operation Mi Jinlong
2011-03-02  6:34 ` [PATCH 12/17] CLNT: test DESTROY_SESSION not the sole operation Mi Jinlong
2011-03-02  6:34 ` [PATCH 13/17] CLNT: add a simple test about RECLAIM_COMPLETE Mi Jinlong
2011-03-02  6:35 ` [PATCH 14/17] CLNT: test reclaim after RECLAIM_COMPLETE Mi Jinlong
2011-03-02  6:36 ` [PATCH 15/17] CLNT: test lock before RECLAIM_COMPLETE Mi Jinlong
2011-03-14 19:27   ` J. Bruce Fields
2011-03-15  3:06     ` Mi Jinlong
2011-03-17 22:54       ` J. Bruce Fields
2011-03-02  6:36 ` [PATCH 16/17] CLNT: test double RECLAIM_COMPLETE after create session Mi Jinlong
2011-03-02  6:37 ` [PATCH 17/17] CLNT: test EXCLUSIVE4_1 for different verifier Mi Jinlong
2011-03-03  5:56 ` [PATCH 00/17] add some test case for pynfs41 J. Bruce Fields
2011-03-28  8:50 ` [PATCH 0/5] a pynfs41 problem and some tests about RECLAIM_COMPLETE Mi Jinlong
2011-03-28  8:57   ` [PATCH 1/5] CLNT: try to destroy session after test complete Mi Jinlong
2011-04-19 15:20     ` J. Bruce Fields
2011-04-20  9:33       ` Mi Jinlong
2011-03-28  8:59   ` [PATCH v2 2/5] CLNT: add a simple test about RECLAIM_COMPLETE Mi Jinlong
2011-03-28  8:59   ` [PATCH v2 3/5] CLNT: test reclaim after RECLAIM_COMPLETE Mi Jinlong
2011-04-19 22:49     ` J. Bruce Fields
2011-03-28  9:00   ` [PATCH v2 4/5] CLNT: test lock before RECLAIM_COMPLETE Mi Jinlong
2011-03-28  9:00   ` [PATCH v2 5/5] CLNT: test double RECLAIM_COMPLETE after create session Mi Jinlong
2011-04-19 22:51   ` [PATCH 0/5] a pynfs41 problem and some tests about RECLAIM_COMPLETE J. Bruce Fields

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=20110303145109.GA11402@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mijinlong@cn.fujitsu.com \
    /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).