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:	Sat, 3 Oct 2015 23:23:13 -0700
From:	Christoph Hellwig <>
To:	Andreas Gruenbacher <>
Cc:	Alexander Viro <>,
	Theodore Ts'o <>,
	Andreas Dilger <>,
	"J. Bruce Fields" <>,
	Jeff Layton <>,
	Trond Myklebust <>,
	Anna Schumaker <>,,,,,
Subject: Re: [PATCH v8 00/41] Richacls

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.

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.  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.

And honestly I tink adding even more overload to xattrs is a really bad
idea and after 10 years of experience with that junk we really need to
learn and make new overloads proper system calls.

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