On Wed, Oct 7, 2015 at 9:50 AM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: > On Tue, Oct 06, 2015 at 02:26:09PM -0600, Andreas Dilger wrote: >> And any disk filesystems that have their own non-POSIX ACLs, such as HFS, NTFS, ZFS would presumably also need to map the in-kernel Richacl format to their on-disk format. > > No, we did this mistake with Posix ACLs, and we're not going to repeat > it here. Filesystems with their own slightly different ACLs must not > reuse the interface. Well, things may not be quite as clearly delineated. We currently have code in nfsd for mapping between NFSv4 ACLs on the wire and POSIX ACLs on local file systems. This mapping is problematic because of the semantic differences between NFSv4 ACLs and POSIX ACLs (different sets of permissions, access and default acl vs. inheritance flags, different permission check algorithm). I wish we could have avoided that. Richacls are designed to support NFSv4 ACLs on top of POSIX systems. This means that they should obviously be supported by the NFSv4 server and client (see the patches) and by the common local filesystems. ACLs on NTFS and ZFS mostly fit into the same model. The big remaining difference there is how users and groups are identified: NTFS used SIDs (https://en.wikipedia.org/wiki/Security_Identifier); ZFS could be said to use a hybrid UID / GID / SID model. Exposing those ACLs as richacls would make sense if we can find a clean way of handling this aspect. HFS ACLs have sufficiently different semantics (the user.group tuples) that representing them as richacls wouldn't make sense. Thanks, Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
