On Aug 01 2016, Seth Forshee <seth.forshee@xxxxxxxxxxxxx> wrote:
> There's also a problem with default acls that I'm not sure there's
> currently a solution for. As far as I can tell FUSE_CREATE doesn't give
> back any indication of whether an existing file was opened or a new file
> was created. Without knowing that I cannot know whether or not the inode
> should inherit default acls from its parent.
Would it be possible for the FUSE file system to implement this
inheritance by a dumb-copy of the ACL-related xattrs of the parent?
This would solve your problem. But in addition to that, it also seems to
me that even if a file system uses default_permissions for ACL handling,
it may want implement a different policy for permission inheritance...
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
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
