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 3/4 v3] 4.1 CLNT: test open before RECLAIM_COMPLETE
Date: Tue, 23 Aug 2011 17:51:40 -0400	[thread overview]
Message-ID: <20110823215140.GF25350@fieldses.org> (raw)
In-Reply-To: <4E4C771B.2030405@cn.fujitsu.com>

On Thu, Aug 18, 2011 at 10:21:15AM +0800, Mi Jinlong wrote:
> Signed-off-by: Mi Jinlong <mijinlong@cn.fujitsu.com>

Same nits as previous ones (comments mostly repeat what the code says,
space needed after comma between function arguments).

Looks reasonable otherwise.

--b.

> ---
>  nfs4.1/server41tests/st_reclaim_complete.py |   21 ++++++++++++++++++++-
>  1 files changed, 20 insertions(+), 1 deletions(-)
> 
> diff --git a/nfs4.1/server41tests/st_reclaim_complete.py b/nfs4.1/server41tests/st_reclaim_complete.py
> index 3940b7b..921d537 100644
> --- a/nfs4.1/server41tests/st_reclaim_complete.py
> +++ b/nfs4.1/server41tests/st_reclaim_complete.py
> @@ -1,6 +1,6 @@
>  from st_create_session import create_session
>  from nfs4_const import *
> -from environment import check, fail, open_file, create_confirm
> +from environment import check, fail, open_file, create_file, create_confirm
>  import nfs4_ops as op
>  import nfs4lib
>  
> @@ -47,3 +47,22 @@ def testReclaimAfterRECC(t, env):
>                      deleg_type=OPEN_DELEGATE_NONE)
>  
>      check(res,NFS4ERR_NO_GRACE)
> +
> +def testOpenBeforeRECC(t, env):
> +    """After a client establishes a new client ID, if non-reclaim
> +       locking operations are done before the RECLAIM_COMPLETE,
> +       error NFS4ERR_GRACE will be returned. rfc5661 18.51.3
> +
> +    FLAGS: reclaim_complete all
> +    CODE: RECC3
> +    """
> +    name = env.testname(t)
> +    c = env.c1.new_client(name)
> +    sess = c.create_session()
> +
> +    fname = "owner_%s" % name
> +    path = sess.c.homedir + [name]
> +
> +    # Try to open file before RECLAIM_COMPLETE
> +    res = create_file(sess, fname, path, access=OPEN4_SHARE_ACCESS_BOTH)
> +    check(res,NFS4ERR_GRACE)
> -- 
> 1.7.6
> 
> 

  reply	other threads:[~2011-08-23 21:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18  2:18 [PATCH 0/4 v3] pynfs41: Add some tests for RECLAIM_COMPLETE Mi Jinlong
2011-08-18  2:19 ` [PATCH 1/4 v3] 4.1 CLNT: add a simple test about RECLAIM_COMPLETE Mi Jinlong
2011-08-23 21:43   ` J. Bruce Fields
2011-08-24  8:26     ` Mi Jinlong
2011-08-18  2:20 ` [PATCH 2/4 v3] 4.1 CLNT: test reclaims after RECLAIM_COMPLETE Mi Jinlong
2011-08-23 21:50   ` J. Bruce Fields
2011-08-18  2:21 ` [PATCH 3/4 v3] 4.1 CLNT: test open before RECLAIM_COMPLETE Mi Jinlong
2011-08-23 21:51   ` J. Bruce Fields [this message]
2011-08-18  2:22 ` [PATCH 4/4 v3] 4.1 CLNT: test RECLAIM_COMPLETE twice Mi Jinlong
2011-08-23 21:52   ` J. Bruce Fields
2011-08-24  8:53 ` [PATCH 1/4 v4] 4.1 CLNT: add a simple test about RECLAIM_COMPLETE Mi Jinlong
2011-08-24  8:53 ` [PATCH 2/4 v4] 4.1 CLNT: test reclaims after RECLAIM_COMPLETE Mi Jinlong
2011-08-24  8:54 ` [PATCH 3/4 v4] 4.1 CLNT: test open before RECLAIM_COMPLETE Mi Jinlong
2011-08-24  8:54 ` [PATCH 4/4 v4] 4.1 CLNT: test RECLAIM_COMPLETE twice Mi Jinlong
2011-08-26 22:41   ` 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=20110823215140.GF25350@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).