| commit | 1947164feb41710842277874cae0c35bfc97e3ab | |
| author | Christian Ambach <ambi@samba.org> | |
| Tue, 25 Sep 2012 01:25:36 +0000 (25 03:25 +0200) | ||
| committer | Christian Ambach <ambi@samba.org> | |
| Thu, 27 Sep 2012 02:36:52 +0000 (27 04:36 +0200) | ||
| tree | 7415bf0ac87ca2a18421ffc64925eecbe680780d | treesnapshot (tar.gz zip) |
| parent | 19631e8e7e7d871261642340ffdcec3f73dccca6 | commitdiff |
s3:nfs4acls filter away inheritance flags on files
While it is possible to define inheritance flags on files on Windows, this will
be denied by GPFS and UFS (and potentially others).
So it will be better to strip of these bits when being set for files instead of
failing to set the ACL completely (this is current behavior).
Users that want to retain the full SD will have to use acl_xattr (acl_tdb), as
other pieces of the SD are also lost when translating to NFSv4. So this should
not be a too intrusive change, but allow users to migrate data with such flags
instead of failing to migrate the ACL completely.
While it is possible to define inheritance flags on files on Windows, this will
be denied by GPFS and UFS (and potentially others).
So it will be better to strip of these bits when being set for files instead of
failing to set the ACL completely (this is current behavior).
Users that want to retain the full SD will have to use acl_xattr (acl_tdb), as
other pieces of the SD are also lost when translating to NFSv4. So this should
not be a too intrusive change, but allow users to migrate data with such flags
instead of failing to migrate the ACL completely.
| source3/modules/nfs4_acls.c | diffblobblamehistory |