From: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
To: linux-nfs@vger.kernel.org, bfields@fieldses.org
Cc: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Subject: [PATCH 2/5] client: test current stateid processing on PUTROOTFH
Date: Sun, 15 Jan 2012 20:05:25 +0100 [thread overview]
Message-ID: <1326654328-20557-3-git-send-email-tigran.mkrtchyan@desy.de> (raw)
In-Reply-To: <1326654328-20557-1-git-send-email-tigran.mkrtchyan@desy.de>
Signed-off-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
---
nfs4.1/server41tests/st_current_stateid.py | 31 ++++++++++++++++++++++++++++
1 files changed, 31 insertions(+), 0 deletions(-)
diff --git a/nfs4.1/server41tests/st_current_stateid.py b/nfs4.1/server41tests/st_current_stateid.py
index 1f24ec9..e2da451 100644
--- a/nfs4.1/server41tests/st_current_stateid.py
+++ b/nfs4.1/server41tests/st_current_stateid.py
@@ -84,3 +84,34 @@ def testLockWriteLocku(t, env):
op.close(0, stateid)]
res = sess1.compound([op.putfh(fh)] + lock_ops)
check(res, NFS4_OK)
+
+def testOpenPutrootfhClose(t, env):
+ """test current state id processing by having OPEN, PUTROOTFH and CLOSE
+ in a single compound
+
+ FLAGS: currentstateid all
+ CODE: CSID5
+ """
+ sess1 = env.c1.new_client_session(env.testname(t))
+
+ open_op = open_create_file_op(sess1, env.testname(t), open_create=OPEN4_CREATE)
+ res = sess1.compound(open_op + [op.putrootfh(), op.close(0, current_stateid)])
+ checklist(res, [NFS4ERR_STALE_STATEID, NFS4ERR_BAD_STATEID])
+
+def testCloseNoStateid(t, env):
+ """test current state id processing by having CLOSE
+ without operation which provides stateid
+
+ FLAGS: currentstateid all
+ CODE: CSID6
+ """
+ sess1 = env.c1.new_client_session(env.testname(t))
+
+ res = create_file(sess1, env.testname(t))
+ check(res)
+ fh = res.resarray[-1].object
+ stateid = res.resarray[-2].stateid
+
+ res = sess1.compound([op.putfh(fh), op.close(0, current_stateid)])
+ checklist(res, [NFS4ERR_STALE_STATEID, NFS4ERR_BAD_STATEID])
+
--
1.7.7.5
next prev parent reply other threads:[~2012-01-15 19:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 19:05 [PATCH 0/5] more test on current stateid processing Tigran Mkrtchyan
2012-01-15 19:05 ` [PATCH 1/5] client: move current stateid test into a dedicated module Tigran Mkrtchyan
2012-01-15 19:05 ` Tigran Mkrtchyan [this message]
2012-01-15 19:05 ` [PATCH 3/5] client: test current stateid processing with OPEN+LAYOUTGET in a single compound Tigran Mkrtchyan
2012-01-15 19:05 ` [PATCH 4/5] client: test current stateid processing with OPEN and SETATTR Tigran Mkrtchyan
2012-01-15 19:05 ` [PATCH 5/5] client: test OPEN+FREE_STETEID+CLOSE in a single compound Tigran Mkrtchyan
2012-01-15 20:54 ` [PATCH 0/5] more test on current stateid processing J. Bruce Fields
2012-01-15 22:31 ` Tiramisu Mokka
2012-01-17 16:42 ` J. Bruce Fields
2012-01-24 11:53 ` Benny Halevy
2012-01-24 12:18 ` Tigran Mkrtchyan
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=1326654328-20557-3-git-send-email-tigran.mkrtchyan@desy.de \
--to=tigran.mkrtchyan@desy.de \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).