>> The remaining question for me then is around the NFSv4 ACL and the >> ownership change permission, and whether I should be able to get that >> to work, especially on a stock system. > > No. When you set an ACL, the server just translates that ACL to the > closet POSIX ACL it can find. And the filesystem code just enforces > that POSIX ACL. POSIX ACLs have no equivalent to WRITE_OWNER. I can't > remember what the code in fs/nfsd/nfs4acl.c does--the only choices would > be to either ignore the bit or fail, I think it does the former. It does the former. The POSIX ACL is stored in a short and the bit for NFS4_ACE_WRITE_OWNER is 0x80000, so it just drops off. > (In theory knfsd could store the full v4 ACL in an extended attribute > and do its own enforcement on the side--I think Samba can do something > like this. This seems complicated to me and I'd rather add richacl > support to the filesystems, but that effort has stalled.) It seems complicated and would split the POSIX ACL code from the NFSv4 ACL code, with little benefit for most people, with more risk due to the extra code to be maintained. Given that all the translation code is already in place, I would be more inclined to leave it as is and maybe store, in addition and optionally, the untranslated NFSv4 ACL separately, so enforcement, which currently works, is left alone in the implementation and representation, which is lacking due to the retranslation back from POSIX ACL to NFSv4 ACL, can be switched on at the server if desired and passed back to the clients. But I digress... I've been looking at this over the last couple of days with the idea of storing the WRITE_OWNER permission as additional extended attribute on the exported filesystem, initially as an array of UIDs/GIDs. I think this should be workable: POSIX ACLs are stored as extended attributes and so this would be in addition to that. Does this seem like a reasonable approach? Would there be much interest in this, if implemented? Cheers, Drew. Drew Leske drew.leske@xxxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
