From: Frank Filz <ffilz-lists@mindspring.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
"J. Bruce Fields" <bfields@redhat.com>
Cc: ffilz-lists@mindspring.com, ffilz@us.ibm.com
Subject: Some pynfs updates
Date: Tue, 11 Jun 2013 10:08:09 -0700 [thread overview]
Message-ID: <51B75979.5070300@mindspring.com> (raw)
Bruce,
Please pull this branch from github:
https://github.com/ffilz/pynfs/commits/master
The git log is below.
Thanks
Frank
commit 2ddd13347e2769801e1c72c8e8d32cef1bcb3fe0
Author: Frank S. Filz <ffilz@us.ibm.com>
Date: Wed May 22 17:11:02 2013 -0700
Make LOOK10 accept MSG_ACCEPTED: GARBAGE_ARGS as well as NFS4ERR_BADXDR
The Ganesha server does XDR for the whole request before starting to
process COMPOUND. As a result, LOOK10 causes an XDR failure that Ganesha
responds at RPC layer and never gets to NFS layer to return NFS4ERR_BADXDR.
Signed-off-by: Frank S. Filz <ffilz@us.ibm.com>
commit 1eda552a5183e71351fc84c53b9561b8a9cab4f1
Author: Frank S. Filz <ffilz@us.ibm.com>
Date: Wed May 1 16:14:41 2013 -0700
Make some tests runable by request
Ganesha can pass several tests that were made inoperable.
The original FLAGS: for these were commented out and FLAGS:
is left blank so these tests only run if requested for.
Plus a few tests had duplicate names.
Signed-off-by: Frank S. Filz <ffilz@us.ibm.com>
commit a6548ab80a68787dc3fcb5c8531d4d189d77c3a9
Author: Frank S. Filz <ffilz@us.ibm.com>
Date: Wed May 1 16:06:56 2013 -0700
Make mode 000 tests expect NFS4_OK when run as root
They will warn if NFS4ERR_ACCESS is returned.
Signed-off-by: Frank S. Filz <ffilz@us.ibm.com>
next reply other threads:[~2013-06-11 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 17:08 Frank Filz [this message]
2013-06-11 20:06 ` Some pynfs updates J. Bruce Fields
2013-06-11 20:22 ` Frank Filz
2013-06-11 20:28 ` J. Bruce Fields
2013-06-11 21:01 ` Frank Filz
2013-06-11 21:01 ` 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=51B75979.5070300@mindspring.com \
--to=ffilz-lists@mindspring.com \
--cc=bfields@redhat.com \
--cc=ffilz@us.ibm.com \
--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 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.