lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 6 Oct 2015 08:17:11 +1100
From:	Dave Chinner <>
To:	Andreas Gruenbacher <>
Cc:	Christoph Hellwig <>,
	Alexander Viro <>,
	Theodore Ts'o <>,
	Andreas Dilger <>,
	"J. Bruce Fields" <>,
	Jeff Layton <>,
	Trond Myklebust <>,
	Anna Schumaker <>,, LKML <>,
	linux-fsdevel <>,,
Subject: Re: [PATCH v8 00/41] Richacls

On Mon, Oct 05, 2015 at 08:45:40PM +0200, Andreas Gruenbacher wrote:
> On Sun, Oct 4, 2015 at 8:23 AM, Christoph Hellwig <> wrote:
> > On Mon, Sep 28, 2015 at 12:08:51AM +0200, Andreas Gruenbacher wrote:
> >> Hello,
> >>
> >> here's another update of the richacl patch queue.  At this stage, I would
> >> like to ask for final feedback so that the core and ext4 code (patches
> >> 1-19) can be merged in the 4.4 merge window.  The nfsd and nfs code should
> >> then go through the respective maintainer trees.
> >
> > Now way in this form even if everyone agrees we should have these
> > bastard ACLs.  I certainly disagree.
> Well, thanks for having a look at the patches.
> > Ayway, back to the VFS <-> FS interface.  You still require tons of
> > boilderplate code in the filesystem which isn't required and we got rid
> > of for Posix ACLs.  The filesystem should not look at the userspace
> > xattr format, please follow a model similar to ->get_acl and ->set_acl
> > for Posix ACLs.
> I will repost a version that has this cleaned up.
> > After that the wire up should be so trivial that you can wire up btrfs,
> > xfs and f2fs as well, which is important to make the feature mergeable.
> Why would the patch queue become more mergeable by having support for
> more filesystems in it? The filesystem specific code really isn't all
> that interesting.

The hardest part for the filesystem support is the on-disk feature
flag that needs to be set. The kernel part of that is easy, but it's
an on-disk format change and so there's also all the userspace side
for mkfs, fsck, debug tools, etc, that also need to be able to parse
and understand it. So while the xattr code can be made much more
generic, there's a bunch of filesystem specific code that needs to
go into multiple different repositories and userspace packages for

Andreas, I also can't remember if any xfstests have been written for
these ACLs? That would certainly help make sure all these
filesystems have equivalent behaviour...


Dave Chinner
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists