From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com ([66.111.4.29]:59503 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754508AbcHAX2D convert rfc822-to-8bit (ORCPT ); Mon, 1 Aug 2016 19:28:03 -0400 From: Nikolaus Rath To: Seth Forshee Cc: fuse-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org, Miklos Szeredi , "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> Date: Mon, 01 Aug 2016 16:03:57 -0700 In-Reply-To: <1470086846-19844-1-git-send-email-seth.forshee@canonical.com> (Seth Forshee's message of "Mon, 1 Aug 2016 16:27:24 -0500") Message-ID: <87d1lsjdlu.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 01 2016, Seth Forshee 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.«