From: Volker Lendecke <Volker.Lendecke@SerNet.DE>
To: Jeremy Allison <jra@samba.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
"J. Bruce Fields" <bfields@fieldses.org>,
Jeff Layton <jlayton@poochiereds.net>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Dave Chinner <david@fromorbit.com>,
linux-ext4@vger.kernel.org, xfs@oss.sgi.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-cifs@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH v21 00/22] Richacls
Date: Tue, 10 May 2016 10:20:22 +0200 [thread overview]
Message-ID: <20160510082022.GC26892@sernet.de> (raw)
In-Reply-To: <20160510081150.GA3411@jeremy-ThinkPad-T430s>
On Tue, May 10, 2016 at 10:11:50AM +0200, Jeremy Allison wrote:
> +1 from me. This is something that many vendors need
> and have needed for a very long time. Getting this
> in will allow *large* amounts of existing storage to
> be migrated to Linux.
ZFS has NFSv4 richacls, and people seem to risk shitstorms
for ZFS. Not only for this of course, but they do
contribute.
Volker
--
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt@sernet.de
next prev parent reply other threads:[~2016-05-10 8:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 22:02 [PATCH v21 00/22] Richacls Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 01/22] vfs: Add IS_ACL() and IS_RICHACL() tests Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 02/22] vfs: Add MAY_CREATE_FILE and MAY_CREATE_DIR permission flags Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 03/22] vfs: Add MAY_DELETE_SELF and MAY_DELETE_CHILD " Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 04/22] vfs: Make the inode passed to inode_change_ok non-const Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 05/22] vfs: Add permission flags for setting file attributes Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 06/22] richacl: In-memory representation and helper functions Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 07/22] richacl: Permission mapping functions Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 08/22] richacl: Compute maximum file masks from an acl Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 09/22] richacl: Permission check algorithm Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 10/22] posix_acl: Improve xattr fixup code Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 11/22] vfs: Cache base_acl objects in inodes Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 12/22] vfs: Add get_richacl and set_richacl inode operations Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 13/22] vfs: Cache richacl in struct inode Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 14/22] richacl: Update the file masks in chmod() Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 15/22] richacl: Check if an acl is equivalent to a file mode Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 16/22] richacl: Create-time inheritance Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 17/22] richacl: Automatic Inheritance Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 18/22] richacl: xattr mapping functions Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 19/22] richacl: Add richacl xattr handler Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 20/22] vfs: Add richacl permission checking Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 21/22] ext4: Add richacl support Andreas Gruenbacher
2016-05-09 22:02 ` [PATCH v21 22/22] ext4: Add richacl feature flag Andreas Gruenbacher
2016-05-10 4:18 ` [PATCH v21 00/22] Richacls Volker Lendecke
2016-05-10 8:11 ` Jeremy Allison
2016-05-10 8:20 ` Volker Lendecke [this message]
2016-05-10 15:55 ` Frank Filz
2016-05-23 1:20 James Johnston
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160510082022.GC26892@sernet.de \
--to=volker.lendecke@sernet.de \
--cc=adilger.kernel@dilger.ca \
--cc=agruenba@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jlayton@poochiereds.net \
--cc=jra@samba.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).