From: "J. Bruce Fields" <bfields@redhat.com>
To: Fred Isaman <iisaman@netapp.com>
Cc: linux-nfs@vger.kernel.org, Mi Jinlong <mijinlong@cn.fujitsu.com>,
"J. Bruce Fields" <bfields@redhat.com>
Subject: [PATCH 0/6] pynfs patches
Date: Thu, 28 Jul 2011 16:02:58 -0400 [thread overview]
Message-ID: <1311883384-20260-1-git-send-email-bfields@redhat.com> (raw)
This fixes a RECLAIM_COMPLETE bug that makes the tests work for me
again.
And also try sharing a few more things between 4.0 and 4.1.
The same patches are available from
git://linux-nfs.org/~bfields/pynfs.git master
My biggest remaining annoyance is that the rename tests all go over the
nfs server's maximum op count. pynfs should really be smart enough to
do the lookups in reasonable chunks. Or we could probably find a
simpler workaround for the rename case.
(And I've also updated by test scripts to use the new merged project, at
git://linux-nfs.org/~bfields/testd.git.)
--b.
J. Bruce Fields (6):
CLNT: provide new_client_session shortcut
CLNT: send RECLAIM_COMPLETE when required
Share showresults.py between 4.0 and 4.1
Make top-level setup.py set up nfs4.0 as well
Merge top-level READMEs
Share testmod.py between nfs4.0 and nfs4.1
README | 17 +-
README-4.1 | 8 -
nfs4.0/lib/testmod.py | 417 +----------------------------------
nfs4.0/showresults.py | 74 ------
nfs4.1/nfs4client.py | 6 +
nfs4.1/server41tests/environment.py | 3 +-
nfs4.1/server41tests/st_block.py | 16 +-
nfs4.1/server41tests/st_open.py | 23 +--
nfs4.1/server41tests/st_rename.py | 108 +++------
nfs4.1/server41tests/st_secinfo.py | 6 +-
nfs4.1/server41tests/st_sequence.py | 9 +-
nfs4.1/showresults.py | 74 ------
setup.py | 6 +-
showresults.py | 74 ++++++
14 files changed, 158 insertions(+), 683 deletions(-)
delete mode 100644 README-4.1
mode change 100644 => 120000 nfs4.0/lib/testmod.py
delete mode 100755 nfs4.0/showresults.py
delete mode 100755 nfs4.1/showresults.py
mode change 100644 => 100755 setup.py
create mode 100755 showresults.py
--
1.7.4.1
next reply other threads:[~2011-07-28 20:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 20:02 J. Bruce Fields [this message]
2011-07-28 20:02 ` [PATCH 1/6] CLNT: provide new_client_session shortcut J. Bruce Fields
2011-07-28 20:03 ` [PATCH 2/6] CLNT: send RECLAIM_COMPLETE when required J. Bruce Fields
2011-07-28 20:03 ` [PATCH 3/6] Share showresults.py between 4.0 and 4.1 J. Bruce Fields
2011-07-28 20:03 ` [PATCH 4/6] Make top-level setup.py set up nfs4.0 as well J. Bruce Fields
2011-07-28 20:03 ` [PATCH 5/6] Merge top-level READMEs J. Bruce Fields
2011-07-28 20:45 ` J. Bruce Fields
2011-07-28 20:03 ` [PATCH 6/6] Share testmod.py between nfs4.0 and nfs4.1 J. Bruce Fields
2011-08-01 22:35 ` [PATCH 0/6] pynfs patches J. Bruce Fields
2011-08-09 20:30 ` two more minor " J. Bruce Fields
2011-08-17 20:54 ` 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=1311883384-20260-1-git-send-email-bfields@redhat.com \
--to=bfields@redhat.com \
--cc=iisaman@netapp.com \
--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).