From: "Frank Filz" <ffilzlnx@mindspring.com>
To: "'J. Bruce Fields'" <bfields@fieldses.org>
Cc: "'J. Bruce Fields'" <bfields@redhat.com>,
"'Linux NFS Mailing List'" <linux-nfs@vger.kernel.org>
Subject: RE: pynfs pull request
Date: Mon, 24 Oct 2016 11:02:55 -0700 [thread overview]
Message-ID: <00bd01d22e20$d8f80610$8ae81230$@mindspring.com> (raw)
In-Reply-To: <20161021155329.GA19831@fieldses.org>
> On Fri, Jul 29, 2016 at 02:55:19PM -0700, Frank Filz wrote:
> > > On Thu, Jul 28, 2016 at 02:09:26PM -0700, Frank Filz wrote:
> > > > Pull master branch from: git://github.com/ffilz/pynfs.git
> > > >
> > > > 6c6ecec ajay nair Added WRT19 to check WRITE operation with
> > > > incorrect permissions and somebody else's stateid 03f0aee Frank S.
> > > > Filz Add
> > > > WRT18 to test 4 writes in single compound updates change each time
> > > > 2fe404f Frank S. Filz Make ACL tests check for support of
> > > > FATTR4_ACL
>
> By the way, Kaleb just noticed that the sense of ACL0 is reversed--it
fails
> when ACLs are supported. I've added the missing "not".
Yea, sorry...
The test "works" for me because Ganesha always advertises ACL support even
when a given filesystem doesn't (either because ACLs aren't enabled on it,
or the FSAL doesn't support ACLs at all). Since my testing is all on
environments that don't support ACLs, it appears to give correct results,
none of the other ACL tests run, and thus they list as omitted rather than
as failures...
Frank
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
prev parent reply other threads:[~2016-10-24 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <037201d1e81e$04a9b9f0$0dfd2dd0$@mindspring.com>
[not found] ` <20160728193855.GF4732@pad>
2016-07-28 21:09 ` pynfs pull request Frank Filz
2016-07-29 21:30 ` J. Bruce Fields
2016-07-29 21:55 ` Frank Filz
2016-08-01 14:42 ` J. Bruce Fields
2016-10-21 15:53 ` J. Bruce Fields
2016-10-24 18:02 ` Frank Filz [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='00bd01d22e20$d8f80610$8ae81230$@mindspring.com' \
--to=ffilzlnx@mindspring.com \
--cc=bfields@fieldses.org \
--cc=bfields@redhat.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 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).