[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHc6FU4dSsqVBJsN3jCAPrEtX5beiJ9Km_g=r53kJ+8iQPOSUA@mail.gmail.com>
Date: Tue, 23 Feb 2016 12:14:35 +0100
From: Andreas Gruenbacher <agruenba@...hat.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
Cc: "J. Bruce Fields" <bfields@...ldses.org>,
linux-ext4 <linux-ext4@...r.kernel.org>,
XFS Developers <xfs@....sgi.com>,
lkml <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
linux-cifs@...r.kernel.org, Linux API <linux-api@...r.kernel.org>,
Dave Chinner <david@...morbit.com>,
Christoph Hellwig <hch@...radead.org>,
Anna Schumaker <anna.schumaker@...app.com>,
Trond Myklebust <trond.myklebust@...marydata.com>,
Jeff Layton <jlayton@...chiereds.net>,
Andreas Dilger <adilger@...ger.ca>
Subject: Re: richacl(7) man page review comments
On Tue, Feb 23, 2016 at 11:58 AM, Michael Kerrisk (man-pages)
<mtk.manpages@...il.com> 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
Powered by blists - more mailing lists