On Tue, Feb 23, 2016 at 11:58 AM, Michael Kerrisk (man-pages) <mtk.manpages@xxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
