It's not "supposedly" broken, it *is* broken. The current behavior was not an intention of the patch that created it, and it violates the documentation that defines how it should behave. I'm really curious in what scenario someone would want to define explicit inherited ACE's for the legacy components of the ACL and also have that explicit definition randomly changed based on the whims of the application and the state of the umask?
As I proposed, if this behavior is desirable, it should result from a new aclinherit setting, not a tunable whose name would be more appropriately "zfs_break_acl_passthrough" 8-/. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/openzfs/openzfs/pull/557#issuecomment-367108858 ------------------------------------------ openzfs-developer Archives: https://openzfs.topicbox.com/groups/developer/discussions/Taa24d3ad3ace2410-Meeae1617bf863e2c607b5da8 Powered by Topicbox: https://topicbox.com
