From: bfields@fieldses.org (J. Bruce Fields)
To: Andreas Gruenbacher <andreas.gruenbacher@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-nfs@vger.kernel.org
Subject: Re: [RFC 00/21] Richacls
Date: Fri, 27 Feb 2015 17:48:46 -0500 [thread overview]
Message-ID: <20150227224846.GB8750@fieldses.org> (raw)
In-Reply-To: <cover.1424907511.git.agruenba@redhat.com>
Thanks for this!
On Thu, Feb 26, 2015 at 12:41:21AM +0100, Andreas Gruenbacher wrote:
> At this point, I would like to ask for your feedback as to what should
> be changed before these patches can be merged, even if merging these
> patches alone doesn't make a while lot of sense. I will follow up
> with additional pieces to the puzzle like the nfsv4 support as I get
> them into shape again.
I remember my main concern being how we collapse the ACL and mask bits
to map a richacl to an NFSv4 (or Samba) ACL. I can't remember what the
compromise there ended up being. I guess I'll watch for that when it
comes.
--b.
next prev parent reply other threads:[~2015-02-27 22:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 23:41 [RFC 00/21] Richacls Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 01/21] vfs: Minor documentation fix Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 02/21] vfs: Shrink struct posix_acl Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 03/21] vfs: Add IS_ACL() and IS_RICHACL() tests Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 04/21] vfs: Add MAY_CREATE_FILE and MAY_CREATE_DIR permission flags Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 05/21] vfs: Add MAY_DELETE_SELF and MAY_DELETE_CHILD " Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 06/21] vfs: Make the inode passed to inode_change_ok non-const Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 07/21] vfs: Add permission flags for setting file attributes Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 08/21] richacl: In-memory representation and helper functions Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 09/21] richacl: Permission mapping functions Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 10/21] richacl: Compute maximum file masks from an acl Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 11/21] richacl: Update the file masks in chmod() Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 12/21] richacl: Permission check algorithm Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 13/21] richacl: Create-time inheritance Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 14/21] richacl: Check if an acl is equivalent to a file mode Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 15/21] richacl: Automatic Inheritance Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 16/21] richacl: xattr mapping functions Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 17/21] vfs: Cache base_acl objects in inodes Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 18/21] vfs: Cache richacl in struct inode Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 19/21] vfs: Add richacl permission checking Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 20/21] ext4: Implement rich acl for ext4 Andreas Gruenbacher
2015-02-25 23:41 ` [RFC 21/21] ext4: Add richacl feature flag Andreas Gruenbacher
2015-02-27 22:48 ` J. Bruce Fields [this message]
2015-02-28 0:11 ` [RFC 00/21] Richacls Andreas Grünbacher
-- strict thread matches above, loose matches on Subject: below --
2015-02-25 23:31 Andreas Gruenbacher
2015-02-26 5:44 ` Michael Kerrisk
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=20150227224846.GB8750@fieldses.org \
--to=bfields@fieldses.org \
--cc=andreas.gruenbacher@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/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