From: Andreas Gruenbacher Subject: Re: richacl(7) man page review comments Date: Tue, 23 Feb 2016 12:14:35 +0100 Message-ID: References: <56B770B6.7040803@gmail.com> <56B77262.7090107@gmail.com> <56C0F23C.7030902@gmail.com> <56CA2EEB.9080504@gmail.com> <56CC3B4A.7070204@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: "J. Bruce Fields" , linux-ext4 , XFS Developers , lkml , linux-fsdevel , Linux NFS Mailing List , linux-cifs@vger.kernel.org, Linux API , Dave Chinner , Christoph Hellwig , Anna Schumaker , Trond Myklebust , Jeff Layton , Andreas Dilger To: "Michael Kerrisk (man-pages)" Return-path: In-Reply-To: <56CC3B4A.7070204@gmail.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On Tue, Feb 23, 2016 at 11:58 AM, Michael Kerrisk (man-pages) wrote: > So, in terms of actually testing this stuff, is it just a matter of > applying your patch series to the kernel, building the kernel, pulling > the RichACL user-space tools from Git, and mount(8)ing a filesystem with > the right option? You'd create a test filesystem with the appropriate feature flag set (mkfs.ext4 -O richacl2 / mkfs.xfs -m richacl=1), RichACLs are not enabled by mount options anymore. This will obviously require versions of e2fsprogs / xfsprogs that understand the feature. If you want coreutils support which isn't strictly necessary, you'll need the patched version too. Other than that, it's really simple. Andreas