lists.openwall.net   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 11:07:46 +0200
From:	Pavel Machek <pavel@....cz>
To:	Andreas Gruenbacher <agruenba@...hat.com>
Cc:	Alexander Viro <viro@...iv.linux.org.uk>,
	Theodore Ts'o <tytso@....edu>,
	Andreas Dilger <adilger.kernel@...ger.ca>,
	"J. Bruce Fields" <bfields@...ldses.org>,
	Jeff Layton <jlayton@...chiereds.net>,
	Trond Myklebust <trond.myklebust@...marydata.com>,
	Anna Schumaker <anna.schumaker@...app.com>,
	linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, linux-nfs@...r.kernel.org,
	linux-api@...r.kernel.org
Subject: Re: [PATCH v9 00/43] Richacls

On Mon 2015-10-05 21:36:27, Andreas Gruenbacher wrote:
> Here is another update of the richacl patch queue.  I would like to ask for
> feedback so that the core and ext4 code (patches 1-21) can be merged in the
> 4.4 merge window.  Changes since the last posting
> (https://lkml.org/lkml/2015/9/27/148):
> 
>  * A set_richacl inode operation similar to set_acl for POSIX ACLs was
>    added.  The filesystem specific code needed for adding richacl support
>    has shrunk: ext4_richacl_chmod, ext4_xattr_{list,get,set}_richacl,
>    ext4_init_richacl, ext4_richacl_xattr_handler were all replaced by vfs
>    functions.
> 
> The complete patch queue is available here:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/agruen/linux-richacl.git \
> 	richacl-2015-10-05
> 
> 
> The richacl user-space utilitites and test suite are available here:
> 
>   https://github.com/andreas-gruenbacher/richacl/
> 
> 
> We still have two open issues in nfs (see the previous posting) which don't
> affect the core functionality.

Should there be file in Documentation/ explaining how this works?

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists