From: Andreas Gruenbacher Subject: Re: [PATCH v11 21/48] ext4: Add richacl feature flag Date: Fri, 16 Oct 2015 19:41:30 +0200 Message-ID: References: <1445008706-15115-1-git-send-email-agruenba@redhat.com> <1445008706-15115-22-git-send-email-agruenba@redhat.com> <5621346E.5000500@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Alexander Viro , "Theodore Ts'o" , Andreas Dilger , "J. Bruce Fields" , Jeff Layton , Trond Myklebust , Anna Schumaker , Dave Chinner , linux-ext4 , xfs@oss.sgi.com, LKML , linux-fsdevel , Linux NFS Mailing List , linux-cifs@vger.kernel.org, Linux API , "Aneesh Kumar K.V" To: Austin S Hemmelgarn Return-path: In-Reply-To: <5621346E.5000500@gmail.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On Fri, Oct 16, 2015 at 7:31 PM, Austin S Hemmelgarn wrote: > I would like to re-iterate, on both XFS and ext4, I _really_ think this > should be a ro_compat flag, and not an incompat one. If a person has the > ability to mount the FS (even if it's a read-only mount), then they by > definition have read access to the file or partition that the filesystem is > contained in, which means that any ACL's stored on the filesystem are > functionally irrelevant, It is unfortunately not safe to make such a file system accessible to other users, so the feature is not strictly read-only compatible. Andreas