Seth Forshee wrote:
Eric and I are working towards adding support for fuse mounts in non-init user namespaces. Towards that end we'd like to add ACL support to fuse as this will allow for a cleaner implementation overall. Below
My best wishes go with you.
is an initial patch to support this. I'd like to get some general feedback on this patch and ask a couple of specific questions. There are some indications that fuse supports ACLs on the userspace side when default_permissions is not used (though I'm not seeing how that works). Will these changes conflict with that support, and if how do we avoid those conflicts?
ntfs-3g has both variants implemented. When supporting ACLs within the userspace, it does not set default_permissions, and it uses null cache timeouts. When expecting ACLs supported at the kernel level, it sets default_permissions and it uses non_null cache timeouts. It sets FUSE_CAP_DONT_MASK in both cases. I would expect default_permissions to make a clear divide between those conditions, avoiding any conflicts. Jean-Pierre -- 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
