From: "J. Bruce Fields" <bfields@fieldses.org>
To: Mi Jinlong <mijinlong@cn.fujitsu.com>
Cc: NFS <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 4/4 v4] 4.1 CLNT: test RECLAIM_COMPLETE twice
Date: Fri, 26 Aug 2011 18:41:49 -0400 [thread overview]
Message-ID: <20110826224149.GA18699@fieldses.org> (raw)
In-Reply-To: <4E54BC35.3060001@cn.fujitsu.com>
Thanks, these four look OK; I'll run a quick test and then push them out
to my repository.
--b.
On Wed, Aug 24, 2011 at 04:54:13PM +0800, Mi Jinlong wrote:
> Signed-off-by: Mi Jinlong <mijinlong@cn.fujitsu.com>
> ---
> nfs4.1/server41tests/st_reclaim_complete.py | 18 ++++++++++++++++++
> 1 files changed, 18 insertions(+), 0 deletions(-)
>
> diff --git a/nfs4.1/server41tests/st_reclaim_complete.py b/nfs4.1/server41tests/st_reclaim_complete.py
> index adb368d..f6baf09 100644
> --- a/nfs4.1/server41tests/st_reclaim_complete.py
> +++ b/nfs4.1/server41tests/st_reclaim_complete.py
> @@ -63,3 +63,21 @@ def testOpenBeforeRECC(t, env):
>
> res = create_file(sess, fname, path, access=OPEN4_SHARE_ACCESS_BOTH)
> check(res, NFS4ERR_GRACE)
> +
> +def testDoubleRECC(t, env):
> + """If RECLAIM_COMPLETE is done a second time, error
> + NFS4ERR_COMPLETE_ALREADY will be returned. rfc5661 18.51.4
> +
> + FLAGS: reclaim_complete all
> + CODE: RECC4
> + """
> + name = env.testname(t)
> + c = env.c1.new_client(name)
> + sess = c.create_session()
> +
> + res = sess.compound([op.reclaim_complete(FALSE)])
> + check(res)
> +
> + # RECLAIM_COMPLETE again
> + res = sess.compound([op.reclaim_complete(FALSE)])
> + check(res, NFS4ERR_COMPLETE_ALREADY)
> --
> 1.7.6
>
>
prev parent reply other threads:[~2011-08-26 22:41 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
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 [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=20110826224149.GA18699@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.