From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com ([66.111.4.26]:48754 "EHLO out2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752065AbcHIAAv convert rfc822-to-8bit (ORCPT ); Mon, 8 Aug 2016 20:00:51 -0400 From: Nikolaus Rath To: Seth Forshee Cc: fuse-devel , linux-fsdevel@vger.kernel.org, "Eric W. Biederman" , Michael j Theall , Jean-Pierre =?utf-8?Q?Andr=C3=A9?= Subject: Re: [RFC v3 0/2] Support for posix acls in fuse References: <1470086846-19844-1-git-send-email-seth.forshee@canonical.com> <87d1lsjdlu.fsf@thinkpad.rath.org> <20160802033931.GA33767@ubuntu-hedt> <1470150838.9444.7.camel@linux.vnet.ibm.com> Date: Mon, 08 Aug 2016 17:00:49 -0700 Message-ID: <878tw63j66.fsf@thinkpad.rath.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Aug 02 2016, Michael Theall wrote: > In case this has any bearing, my filesystem would in fact interpret the > ACLs from the xattrs in order to apply them to the backing filesystem > (which supports ACLs but through a non-xattr interface). In my > particular case, it would be okay for the kernel to assume the > inherited ACLs since it should be the same as if the kernel requested > the ACLs after creation. If I'm not mistaken, this means your file system will however be broken by this change: - Remove passthrough of acl xattrs when fuse acl support is disabled or default_permissions is not used. I assume you don't use default_permissons (because otherwise you couldn't support ACLs), so this means with the patch you would no longer get the ACLs in xattr forms. 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.«