From: "J. Bruce Fields" <bfields@fieldses.org>
To: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/3] client: test OPEN+WRITE+CLOSE in a single compound
Date: Mon, 12 Dec 2011 17:42:19 -0500 [thread overview]
Message-ID: <20111212224219.GC22927@fieldses.org> (raw)
In-Reply-To: <1323721588-8259-1-git-send-email-tigran.mkrtchyan@desy.de>
I already applied some previous version of these--could you check
git://linux-nfs.org/~bfields/pynfs.git
and let me know if I got anything wrong? (If so, incremental patches on
top of that would be appreciated.
Thanks--b.
On Mon, Dec 12, 2011 at 09:26:26PM +0100, Tigran Mkrtchyan wrote:
>
> Signed-off-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
> ---
> nfs4.1/server41tests/st_open.py | 16 ++++++++++++++++
> 1 files changed, 16 insertions(+), 0 deletions(-)
>
> diff --git a/nfs4.1/server41tests/st_open.py b/nfs4.1/server41tests/st_open.py
> index 1c965b2..c809c95 100644
> --- a/nfs4.1/server41tests/st_open.py
> +++ b/nfs4.1/server41tests/st_open.py
> @@ -275,3 +275,19 @@ def testLockLockU(t, env):
> op.locku(WRITE_LT, 0, current_stateid, 0, NFS4_UINT64_MAX) ]
> res = sess1.compound([op.putfh(fh)] + lock_ops)
> check(res, NFS4_OK)
> +
> +def testOpenWriteClose(t, env):
> + """test current state id processing by having OPEN, WRITE and CLOSE
> + in a single compound
> +
> + FLAGS: open all
> + CODE: OPEN33
> + """
> + current_stateid = stateid4(1, '\0' * 12)
> + sess1 = env.c1.new_client_session(env.testname(t))
> +
> + data = "write test data"
> + open_op = open_create_file_op(sess1, env.testname(t), open_create=OPEN4_CREATE)
> + res = sess1.compound(open_op + [op.write(current_stateid, 5, FILE_SYNC4, data),
> + op.close(0, current_stateid)])
> + check(res, NFS4_OK)
> \ No newline at end of file
> --
> 1.7.7
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-12-12 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 20:26 [PATCH 1/3] client: test OPEN+WRITE+CLOSE in a single compound Tigran Mkrtchyan
2011-12-12 20:26 ` [PATCH 2/3] client: test LOCK+WRITE+LOCKU " Tigran Mkrtchyan
2011-12-12 20:26 ` [PATCH 3/3] client: group test with currentstateid tougheter Tigran Mkrtchyan
2011-12-12 22:42 ` J. Bruce Fields [this message]
2011-12-12 22:43 ` [PATCH 1/3] client: test OPEN+WRITE+CLOSE in a single compound J. Bruce Fields
2011-12-12 22:44 ` 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=20111212224219.GC22927@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tigran.mkrtchyan@desy.de \
/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