From: Christoph Hellwig Subject: Re: [PATCH v8 00/41] Richacls Date: Wed, 7 Oct 2015 00:50:54 -0700 Message-ID: <20151007075053.GA8660@infradead.org> References: <1443391772-10171-1-git-send-email-agruenba@redhat.com> <20151004062313.GA20212@infradead.org> <5612C85C.2060407@gmail.com> <20151006094935.GA14144@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andreas Gruenbacher , Christoph Hellwig , Austin S Hemmelgarn , Alexander Viro , Theodore Ts'o , "J. Bruce Fields" , Jeff Layton , Trond Myklebust , Anna Schumaker , linux-ext4 , LKML , linux-fsdevel , linux-nfs@vger.kernel.org, Linux API To: Andreas Dilger Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On Tue, Oct 06, 2015 at 02:26:09PM -0600, Andreas Dilger wrote: > And any disk filesystems that have their own non-POSIX ACLs, such as HFS, NTFS, ZFS would presumably also need to map the in-kernel Richacl format to their on-disk format. No, we did this mistake with Posix ACLs, and we're not going to repeat it here. Filesystems with their own slightly different ACLs must not reuse the interface.