generic/529: use an ACL that doesn't confuse NFS

For historical reasons having to do with Solaris ACL behavior, the Linux
client treats an ACL like the one used as an example here as equivalent
to a mode, causing listxattr to report that no ACL is set on the file.

(See the comment at the top of fs/nfs_common/nfsacl.c in the kernel
source for details, and the "bogus ACL_MASK entry" comment in the same
source file.)  This causes a spurious generic/529 failure on NFS.

As far as I can tell any ACL should trigger the original XFS problem.
So, modify it so as not to hit this odd NFS corner case.

Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Reviewed-by: Eryu Guan <guaneryu@gmail.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
This commit is contained in:
J. Bruce Fields
2019-12-19 17:33:36 -05:00
committed by Eryu Guan
parent 6a31c46b1a
commit dda94e8088
+1 -1
View File
@@ -59,7 +59,7 @@ int main(int argc, char *argv[])
.e = { .e = {
{htole16(1), 0, 0}, {htole16(1), 0, 0},
{htole16(4), 0, 0}, {htole16(4), 0, 0},
{htole16(0x10), 0, 0}, {htole16(0x10), htole16(4), 0},
{htole16(0x20), 0, 0}, {htole16(0x20), 0, 0},
}, },
}; };