Displaying 2 results from an estimated 2 matches for "nfs4acl_xattr_owner_who".
2018 Apr 06
0
Operation Not Supported error for GETXATTR when VFS plugin "nfs4acl_xattr" is used
...c/idl/nfs4acl.idl
@@ -13,7 +13,7 @@ import "misc.idl", "security.idl";
]
interface nfs4acl_interface
{
- const char *NFS4ACL_NDR_XATTR_NAME = "system.nfs4acl";
+ const char *NFS4ACL_NDR_XATTR_NAME = "security.nfs4acl_ndr";
const char *NFS4ACL_XATTR_OWNER_WHO = "OWNER@";
const char *NFS4ACL_XATTR_GROUP_WHO = "GROUP@";
2018 Apr 06
2
Operation Not Supported error for GETXATTR when VFS plugin "nfs4acl_xattr" is used
Hi All
I found there is one bug in the plugin. The name of the attribute for ACL
as per strace output of nfs4_setfacl is *system.nfs4_acl.*
The source code has defined it as
#define NFS4ACL_XATTR_NAME ( "system.nfs4acl" )
Note there is missing underscore.
After this, the EOPNOTSUPP error is not observed.
Hope this helps
Akash
On Thu, Apr 5, 2018 at 11:43 PM, Jeremy Allison