From: "Frank Filz" <ffilzlnx@mindspring.com> To: "'Andreas Gruenbacher'" <andreas.gruenbacher@gmail.com>, <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>, <linux-nfs@vger.kernel.org> Subject: RE: [RFC v3 20/45] richacl: Automatic Inheritance Date: Wed, 13 May 2015 11:01:35 -0700 [thread overview] Message-ID: <0b2401d08da6$dad0d0f0$907272d0$@mindspring.com> (raw) In-Reply-To: <28e2cd75064ff56bad897b6f69356f4fb15b8128.1429868795.git.agruenba@redhat.com> > -----Original Message----- > From: linux-nfs-owner@vger.kernel.org [mailto:linux-nfs- > owner@vger.kernel.org] On Behalf Of Andreas Gruenbacher > Sent: Friday, April 24, 2015 4:04 AM > To: linux-kernel@vger.kernel.org; linux-fsdevel@vger.kernel.org; linux- > nfs@vger.kernel.org > Subject: [RFC v3 20/45] richacl: Automatic Inheritance > > Automatic Inheritance (AI) allows changes to the acl of a directory to > recursively propagate down to files and directories in the directory. > > To implement this, the kernel keeps track of which permissions have been > inherited, and makes sure that permission propagation is turned off when > the file permission bits of a file are changed (upon create or chmod). > > The actual permission propagation is implemented in user space. > > Automatic Inheritance works as follows: > > - When the ACL4_AUTO_INHERIT flag in the acl of a file is not set, the > file is not affected by AI. > > - When the ACL4_AUTO_INHERIT flag in the acl of a directory is set and > a file or subdirectory is created in that directory, files created in > the directory will have the ACL4_AUTO_INHERIT flag set, and all > inherited aces will have the ACE4_INHERITED_ACE flag set. This > allows user space to distinguish between aces which have been > inherited and aces which have been explicitly added. > > - When the ACL4_PROTECTED acl flag in the acl of a file is set, AI will > not modify the acl of the file. This does not affect propagation of > permissions from the file to its children (if the file is a > directory). You might want to edit your commit message to use RICHACL_ instead of ACL4_ constants... > Linux does not have a way of creating files without setting the file permission > bits, so all files created inside a directory with ACL4_AUTO_INHERIT set will > also have the ACL4_PROTECTED flag set. This effectively disables Automatic > Inheritance. > > Protocols which support creating files without specifying permissions can > explicitly clear the ACL4_PROTECTED flag after creating a file and reset the file > masks to "undo" applying the create mode; see > richacl_compute_max_masks(). > This is a workaround; a mechanism that would allow a process to indicate to > the kernel to ignore the create mode when there are inherited permissions > would fix this problem. I'm unclear what will actually be supported for inherited ACLs here. Is this saying that on a pure-Linux system even with Linux NFS client and Linux NFS server, we still would not see inheritance since the mode will always be present on create? My interest here is in how we will tie the Ganesha user space NFS server into this feature. Frank > Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com> > --- > fs/richacl_base.c | 10 +++++++++- > fs/richacl_inode.c | 7 ++++++- > include/linux/richacl.h | 25 +++++++++++++++++++++++-- > 3 files changed, 38 insertions(+), 4 deletions(-) > > diff --git a/fs/richacl_base.c b/fs/richacl_base.c index 54cb482..572f1b8 > 100644 > --- a/fs/richacl_base.c > +++ b/fs/richacl_base.c > @@ -352,7 +352,8 @@ richacl_chmod(struct richacl *acl, mode_t mode) > if (acl->a_owner_mask == owner_mask && > acl->a_group_mask == group_mask && > acl->a_other_mask == other_mask && > - (acl->a_flags & RICHACL_MASKED)) > + (acl->a_flags & RICHACL_MASKED) && > + (!richacl_is_auto_inherit(acl) || richacl_is_protected(acl))) > return acl; > > clone = richacl_clone(acl, GFP_KERNEL); @@ -364,6 +365,8 @@ > richacl_chmod(struct richacl *acl, mode_t mode) > clone->a_owner_mask = owner_mask; > clone->a_group_mask = group_mask; > clone->a_other_mask = other_mask; > + if (richacl_is_auto_inherit(clone)) > + clone->a_flags |= RICHACL_PROTECTED; > > return clone; > } > @@ -434,6 +437,11 @@ richacl_inherit(const struct richacl *dir_acl, int isdir) > ace++; > } > } > + if (richacl_is_auto_inherit(dir_acl)) { > + acl->a_flags = RICHACL_AUTO_INHERIT; > + richacl_for_each_entry(ace, acl) > + ace->e_flags |= RICHACE_INHERITED_ACE; > + } > > return acl; > } > diff --git a/fs/richacl_inode.c b/fs/richacl_inode.c index 1a5b868..dfbb15a > 100644 > --- a/fs/richacl_inode.c > +++ b/fs/richacl_inode.c > @@ -223,9 +223,14 @@ richacl_inherit_inode(const struct richacl *dir_acl, > struct inode *inode) > > acl = richacl_inherit(dir_acl, S_ISDIR(inode->i_mode)); > if (acl) { > + /* > + * We need to set RICHACL_PROTECTED because we are > + * doing an implicit chmod > + */ > + if (richacl_is_auto_inherit(acl)) > + acl->a_flags |= RICHACL_PROTECTED; > > richacl_compute_max_masks(acl); > - > /* > * Ensure that the acl will not grant any permissions beyond > * the create mode. > diff --git a/include/linux/richacl.h b/include/linux/richacl.h index > 8a92b89..bcc2b64 100644 > --- a/include/linux/richacl.h > +++ b/include/linux/richacl.h > @@ -53,9 +53,15 @@ struct richacl { > _ace--) > > /* a_flag values */ > +#define RICHACL_AUTO_INHERIT 0x01 > +#define RICHACL_PROTECTED 0x02 > +#define RICHACL_DEFAULTED 0x04 > #define RICHACL_MASKED 0x80 > > -#define RICHACL_VALID_FLAGS ( \ > +#define RICHACL_VALID_FLAGS ( \ > + RICHACL_AUTO_INHERIT | \ > + RICHACL_PROTECTED | \ > + RICHACL_DEFAULTED | \ > RICHACL_MASKED) > > /* e_type values */ > @@ -68,6 +74,7 @@ struct richacl { > #define RICHACE_NO_PROPAGATE_INHERIT_ACE 0x0004 > #define RICHACE_INHERIT_ONLY_ACE 0x0008 > #define RICHACE_IDENTIFIER_GROUP 0x0040 > +#define RICHACE_INHERITED_ACE 0x0080 > #define RICHACE_SPECIAL_WHO 0x4000 > > #define RICHACE_VALID_FLAGS ( \ > @@ -76,6 +83,7 @@ struct richacl { > RICHACE_NO_PROPAGATE_INHERIT_ACE | \ > RICHACE_INHERIT_ONLY_ACE | \ > RICHACE_IDENTIFIER_GROUP | \ > + RICHACE_INHERITED_ACE | \ > RICHACE_SPECIAL_WHO) > > /* e_mask bitflags */ > @@ -187,6 +195,18 @@ extern void set_cached_richacl(struct inode *, struct > richacl *); extern void forget_cached_richacl(struct inode *); extern struct > richacl *get_richacl(struct inode *); > > +static inline int > +richacl_is_auto_inherit(const struct richacl *acl) { > + return acl->a_flags & RICHACL_AUTO_INHERIT; } > + > +static inline int > +richacl_is_protected(const struct richacl *acl) { > + return acl->a_flags & RICHACL_PROTECTED; } > + > /** > * richace_is_owner - check if @ace is an OWNER@ entry > */ > @@ -257,7 +277,8 @@ richace_clear_inheritance_flags(struct richace *ace) > ace->e_flags &= ~(RICHACE_FILE_INHERIT_ACE | > RICHACE_DIRECTORY_INHERIT_ACE | > RICHACE_NO_PROPAGATE_INHERIT_ACE | > - RICHACE_INHERIT_ONLY_ACE); > + RICHACE_INHERIT_ONLY_ACE | > + RICHACE_INHERITED_ACE); > } > > /** > -- > 2.1.0 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the > body of a message to majordomo@vger.kernel.org More majordomo info at > http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: "Frank Filz" <ffilzlnx-mn4gwa5WIIQysxA8WJXlww@public.gmane.org> To: "'Andreas Gruenbacher'" <andreas.gruenbacher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, <linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, <linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> Subject: RE: [RFC v3 20/45] richacl: Automatic Inheritance Date: Wed, 13 May 2015 11:01:35 -0700 [thread overview] Message-ID: <0b2401d08da6$dad0d0f0$907272d0$@mindspring.com> (raw) In-Reply-To: <28e2cd75064ff56bad897b6f69356f4fb15b8128.1429868795.git.agruenba-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> > -----Original Message----- > From: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org [mailto:linux-nfs- > owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org] On Behalf Of Andreas Gruenbacher > Sent: Friday, April 24, 2015 4:04 AM > To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; linux- > nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org > Subject: [RFC v3 20/45] richacl: Automatic Inheritance > > Automatic Inheritance (AI) allows changes to the acl of a directory to > recursively propagate down to files and directories in the directory. > > To implement this, the kernel keeps track of which permissions have been > inherited, and makes sure that permission propagation is turned off when > the file permission bits of a file are changed (upon create or chmod). > > The actual permission propagation is implemented in user space. > > Automatic Inheritance works as follows: > > - When the ACL4_AUTO_INHERIT flag in the acl of a file is not set, the > file is not affected by AI. > > - When the ACL4_AUTO_INHERIT flag in the acl of a directory is set and > a file or subdirectory is created in that directory, files created in > the directory will have the ACL4_AUTO_INHERIT flag set, and all > inherited aces will have the ACE4_INHERITED_ACE flag set. This > allows user space to distinguish between aces which have been > inherited and aces which have been explicitly added. > > - When the ACL4_PROTECTED acl flag in the acl of a file is set, AI will > not modify the acl of the file. This does not affect propagation of > permissions from the file to its children (if the file is a > directory). You might want to edit your commit message to use RICHACL_ instead of ACL4_ constants... > Linux does not have a way of creating files without setting the file permission > bits, so all files created inside a directory with ACL4_AUTO_INHERIT set will > also have the ACL4_PROTECTED flag set. This effectively disables Automatic > Inheritance. > > Protocols which support creating files without specifying permissions can > explicitly clear the ACL4_PROTECTED flag after creating a file and reset the file > masks to "undo" applying the create mode; see > richacl_compute_max_masks(). > This is a workaround; a mechanism that would allow a process to indicate to > the kernel to ignore the create mode when there are inherited permissions > would fix this problem. I'm unclear what will actually be supported for inherited ACLs here. Is this saying that on a pure-Linux system even with Linux NFS client and Linux NFS server, we still would not see inheritance since the mode will always be present on create? My interest here is in how we will tie the Ganesha user space NFS server into this feature. Frank > Signed-off-by: Andreas Gruenbacher <agruenba-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> > --- > fs/richacl_base.c | 10 +++++++++- > fs/richacl_inode.c | 7 ++++++- > include/linux/richacl.h | 25 +++++++++++++++++++++++-- > 3 files changed, 38 insertions(+), 4 deletions(-) > > diff --git a/fs/richacl_base.c b/fs/richacl_base.c index 54cb482..572f1b8 > 100644 > --- a/fs/richacl_base.c > +++ b/fs/richacl_base.c > @@ -352,7 +352,8 @@ richacl_chmod(struct richacl *acl, mode_t mode) > if (acl->a_owner_mask == owner_mask && > acl->a_group_mask == group_mask && > acl->a_other_mask == other_mask && > - (acl->a_flags & RICHACL_MASKED)) > + (acl->a_flags & RICHACL_MASKED) && > + (!richacl_is_auto_inherit(acl) || richacl_is_protected(acl))) > return acl; > > clone = richacl_clone(acl, GFP_KERNEL); @@ -364,6 +365,8 @@ > richacl_chmod(struct richacl *acl, mode_t mode) > clone->a_owner_mask = owner_mask; > clone->a_group_mask = group_mask; > clone->a_other_mask = other_mask; > + if (richacl_is_auto_inherit(clone)) > + clone->a_flags |= RICHACL_PROTECTED; > > return clone; > } > @@ -434,6 +437,11 @@ richacl_inherit(const struct richacl *dir_acl, int isdir) > ace++; > } > } > + if (richacl_is_auto_inherit(dir_acl)) { > + acl->a_flags = RICHACL_AUTO_INHERIT; > + richacl_for_each_entry(ace, acl) > + ace->e_flags |= RICHACE_INHERITED_ACE; > + } > > return acl; > } > diff --git a/fs/richacl_inode.c b/fs/richacl_inode.c index 1a5b868..dfbb15a > 100644 > --- a/fs/richacl_inode.c > +++ b/fs/richacl_inode.c > @@ -223,9 +223,14 @@ richacl_inherit_inode(const struct richacl *dir_acl, > struct inode *inode) > > acl = richacl_inherit(dir_acl, S_ISDIR(inode->i_mode)); > if (acl) { > + /* > + * We need to set RICHACL_PROTECTED because we are > + * doing an implicit chmod > + */ > + if (richacl_is_auto_inherit(acl)) > + acl->a_flags |= RICHACL_PROTECTED; > > richacl_compute_max_masks(acl); > - > /* > * Ensure that the acl will not grant any permissions beyond > * the create mode. > diff --git a/include/linux/richacl.h b/include/linux/richacl.h index > 8a92b89..bcc2b64 100644 > --- a/include/linux/richacl.h > +++ b/include/linux/richacl.h > @@ -53,9 +53,15 @@ struct richacl { > _ace--) > > /* a_flag values */ > +#define RICHACL_AUTO_INHERIT 0x01 > +#define RICHACL_PROTECTED 0x02 > +#define RICHACL_DEFAULTED 0x04 > #define RICHACL_MASKED 0x80 > > -#define RICHACL_VALID_FLAGS ( \ > +#define RICHACL_VALID_FLAGS ( \ > + RICHACL_AUTO_INHERIT | \ > + RICHACL_PROTECTED | \ > + RICHACL_DEFAULTED | \ > RICHACL_MASKED) > > /* e_type values */ > @@ -68,6 +74,7 @@ struct richacl { > #define RICHACE_NO_PROPAGATE_INHERIT_ACE 0x0004 > #define RICHACE_INHERIT_ONLY_ACE 0x0008 > #define RICHACE_IDENTIFIER_GROUP 0x0040 > +#define RICHACE_INHERITED_ACE 0x0080 > #define RICHACE_SPECIAL_WHO 0x4000 > > #define RICHACE_VALID_FLAGS ( \ > @@ -76,6 +83,7 @@ struct richacl { > RICHACE_NO_PROPAGATE_INHERIT_ACE | \ > RICHACE_INHERIT_ONLY_ACE | \ > RICHACE_IDENTIFIER_GROUP | \ > + RICHACE_INHERITED_ACE | \ > RICHACE_SPECIAL_WHO) > > /* e_mask bitflags */ > @@ -187,6 +195,18 @@ extern void set_cached_richacl(struct inode *, struct > richacl *); extern void forget_cached_richacl(struct inode *); extern struct > richacl *get_richacl(struct inode *); > > +static inline int > +richacl_is_auto_inherit(const struct richacl *acl) { > + return acl->a_flags & RICHACL_AUTO_INHERIT; } > + > +static inline int > +richacl_is_protected(const struct richacl *acl) { > + return acl->a_flags & RICHACL_PROTECTED; } > + > /** > * richace_is_owner - check if @ace is an OWNER@ entry > */ > @@ -257,7 +277,8 @@ richace_clear_inheritance_flags(struct richace *ace) > ace->e_flags &= ~(RICHACE_FILE_INHERIT_ACE | > RICHACE_DIRECTORY_INHERIT_ACE | > RICHACE_NO_PROPAGATE_INHERIT_ACE | > - RICHACE_INHERIT_ONLY_ACE); > + RICHACE_INHERIT_ONLY_ACE | > + RICHACE_INHERITED_ACE); > } > > /** > -- > 2.1.0 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the > body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at > http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-13 18:14 UTC|newest] Thread overview: 154+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-24 11:03 [RFC v3 00/45] Richacls Andreas Gruenbacher 2015-04-24 11:03 ` Andreas Gruenbacher 2015-04-24 11:03 ` [RFC v3 01/45] vfs: Minor documentation fix Andreas Gruenbacher 2015-04-24 11:03 ` [RFC v3 02/45] uapi: Remove kernel internal declaration Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 03/45] nfsd: Checking for acl support does not require fetching any acls Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 04/45] vfs: Shrink struct posix_acl Andreas Gruenbacher 2015-04-25 7:56 ` Rasmus Villemoes 2015-04-27 10:27 ` Andreas Grünbacher 2015-04-24 11:04 ` [RFC v3 05/45] vfs: Add IS_ACL() and IS_RICHACL() tests Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 06/45] vfs: Add MAY_CREATE_FILE and MAY_CREATE_DIR permission flags Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 07/45] vfs: Add MAY_DELETE_SELF and MAY_DELETE_CHILD " Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 08/45] vfs: Make the inode passed to inode_change_ok non-const Andreas Gruenbacher 2015-04-24 11:04 ` Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 09/45] vfs: Add permission flags for setting file attributes Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 10/45] richacl: In-memory representation and helper functions Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 11/45] richacl: Permission mapping functions Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 12/45] richacl: Compute maximum file masks from an acl Andreas Gruenbacher 2015-05-12 21:44 ` J. Bruce Fields 2015-04-24 11:04 ` [RFC v3 13/45] richacl: Update the file masks in chmod() Andreas Gruenbacher 2015-04-24 11:04 ` Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 14/45] richacl: Permission check algorithm Andreas Gruenbacher 2015-04-24 11:04 ` Andreas Gruenbacher 2015-05-22 21:08 ` J. Bruce Fields 2015-05-27 11:25 ` Andreas Grünbacher 2015-05-27 15:05 ` J. Bruce Fields 2015-04-24 11:04 ` [RFC v3 15/45] vfs: Cache base_acl objects in inodes Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 16/45] vfs: Cache richacl in struct inode Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 17/45] richacl: Create-time inheritance Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 18/45] richacl: Check if an acl is equivalent to a file mode Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 19/45] richacl: Also recognize nontrivial mode-equivalent acls Andreas Gruenbacher 2015-05-14 19:28 ` J. Bruce Fields 2015-05-15 20:04 ` J. Bruce Fields 2015-05-15 20:04 ` J. Bruce Fields 2015-05-15 20:51 ` J. Bruce Fields 2015-05-15 20:51 ` J. Bruce Fields 2015-05-27 9:24 ` Andreas Grünbacher 2015-05-27 15:06 ` J. Bruce Fields 2015-05-27 15:06 ` J. Bruce Fields 2015-04-24 11:04 ` [RFC v3 20/45] richacl: Automatic Inheritance Andreas Gruenbacher 2015-05-13 18:01 ` Frank Filz [this message] 2015-05-13 18:01 ` Frank Filz 2015-05-13 20:22 ` Andreas Grünbacher 2015-05-13 20:22 ` Andreas Grünbacher 2015-05-13 20:28 ` Jeremy Allison 2015-05-13 20:28 ` Jeremy Allison 2015-05-13 20:47 ` Andreas Grünbacher 2015-05-13 20:47 ` Andreas Grünbacher 2015-05-13 20:55 ` Jeremy Allison 2015-05-13 20:55 ` Jeremy Allison 2015-05-13 21:15 ` Andreas Grünbacher 2015-05-13 21:15 ` Andreas Grünbacher 2015-05-13 20:38 ` Frank Filz 2015-05-13 20:38 ` Frank Filz 2015-05-13 21:05 ` Andreas Grünbacher 2015-05-13 22:56 ` Frank Filz 2015-05-13 22:56 ` Frank Filz 2015-05-13 23:52 ` Andreas Grünbacher 2015-05-14 15:09 ` J. Bruce Fields 2015-05-14 15:09 ` J. Bruce Fields 2015-05-18 20:39 ` Andreas Grünbacher 2015-05-18 20:39 ` Andreas Grünbacher 2015-05-18 20:43 ` J. Bruce Fields 2015-05-18 20:43 ` J. Bruce Fields 2015-04-24 11:04 ` [RFC v3 21/45] richacl: xattr mapping functions Andreas Gruenbacher 2015-04-24 11:04 ` Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 22/45] vfs: Add richacl permission checking Andreas Gruenbacher 2015-04-24 11:04 ` Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 23/45] ext4: Add richacl support Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 24/45] ext4: Add richacl feature flag Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 25/45] richacl: acl editing helper functions Andreas Gruenbacher 2015-04-24 11:04 ` Andreas Gruenbacher 2015-05-15 21:33 ` J. Bruce Fields 2015-05-15 21:33 ` J. Bruce Fields 2015-04-24 11:04 ` [RFC v3 26/45] richacl: Move everyone@ aces down the acl Andreas Gruenbacher 2015-05-18 21:20 ` J. Bruce Fields 2015-04-24 11:04 ` [RFC v3 27/45] richacl: Propagate everyone@ permissions to other aces Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 28/45] richacl: Isolate the owner and group classes Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 29/45] richacl: Apply the file masks to a richacl Andreas Gruenbacher 2015-05-26 21:56 ` J. Bruce Fields 2015-05-26 21:56 ` J. Bruce Fields 2015-04-24 11:04 ` [RFC v3 30/45] richacl: Create richacl from mode values Andreas Gruenbacher 2015-05-28 19:24 ` J. Bruce Fields 2015-05-28 19:24 ` J. Bruce Fields 2015-05-28 19:25 ` J. Bruce Fields 2015-05-28 19:58 ` Andreas Grünbacher 2015-05-28 19:58 ` Andreas Grünbacher 2015-04-24 11:04 ` [RFC v3 31/45] richacl: Create acl with masks applied in richacl_from_mode() Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 32/45] nfsd: Remove dead declarations Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 33/45] nfsd: Keep list of acls to dispose of in compoundargs Andreas Gruenbacher 2015-05-28 19:52 ` J. Bruce Fields 2015-05-28 19:52 ` J. Bruce Fields 2015-05-28 20:28 ` Andreas Grünbacher 2015-05-28 20:28 ` Andreas Grünbacher 2015-04-24 11:04 ` [RFC v3 34/45] nfsd: Use richacls as internal acl representation Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 35/45] nfsd: Add richacl support Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 36/45] NFSv4: Fix GETATTR bitmap verification Andreas Gruenbacher 2015-05-28 20:33 ` J. Bruce Fields 2015-05-28 20:33 ` J. Bruce Fields 2015-05-28 20:50 ` Trond Myklebust 2015-05-28 20:50 ` Trond Myklebust 2015-05-28 21:05 ` Andreas Grünbacher 2015-05-28 21:05 ` Andreas Grünbacher 2015-05-28 21:40 ` Trond Myklebust 2015-05-28 21:40 ` Trond Myklebust 2015-05-28 21:55 ` Trond Myklebust 2015-05-28 21:55 ` Trond Myklebust 2015-05-28 22:09 ` Andreas Grünbacher 2015-05-28 22:09 ` Andreas Grünbacher 2015-05-28 22:24 ` Trond Myklebust 2015-05-28 22:24 ` Trond Myklebust 2015-05-28 22:28 ` Andreas Grünbacher 2015-05-28 21:15 ` Andreas Grünbacher 2015-05-28 21:28 ` Andreas Grünbacher 2015-05-28 21:28 ` Andreas Grünbacher 2015-04-24 11:04 ` [RFC v3 37/45] nfs/sunrpc: No more encode and decode function pointer casting Andreas Gruenbacher 2015-05-28 23:11 ` Trond Myklebust 2015-05-28 23:40 ` Andreas Grünbacher 2015-05-29 0:37 ` Trond Myklebust 2015-05-29 0:37 ` Trond Myklebust 2015-05-29 15:30 ` Andreas Grünbacher 2015-05-29 15:30 ` Andreas Grünbacher 2015-04-24 11:04 ` [RFC v3 38/45] nfs/sunrpc: Return status code from encode functions Andreas Gruenbacher 2015-05-28 23:39 ` Trond Myklebust 2015-05-28 23:39 ` Trond Myklebust 2015-04-24 11:04 ` [RFC v3 39/45] nfs3: Return posix acl encode errors Andreas Gruenbacher 2015-04-24 11:04 ` Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 40/45] nfs: Remove unused xdr page offsets in getacl/setacl arguments Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 41/45] rpc: Allow to demand-allocate pages to encode into Andreas Gruenbacher 2015-05-28 23:24 ` Trond Myklebust 2015-05-28 23:24 ` Trond Myklebust 2015-05-29 15:46 ` Andreas Grünbacher 2015-04-24 11:04 ` [RFC v3 42/45] nfs: Add richacl support Andreas Gruenbacher 2015-05-28 23:06 ` Trond Myklebust 2015-05-28 23:29 ` Andreas Grünbacher 2015-05-29 13:15 ` Trond Myklebust 2015-05-29 15:00 ` Andreas Grünbacher 2015-05-29 15:24 ` Trond Myklebust 2015-05-29 15:45 ` Andreas Grünbacher 2015-05-29 15:54 ` Trond Myklebust 2015-05-29 15:54 ` Trond Myklebust 2015-05-29 15:54 ` Frank Filz 2015-05-29 15:54 ` Frank Filz 2016-06-23 16:37 ` Weston Andros Adamson 2016-06-23 17:15 ` Frank Filz 2016-07-15 8:00 ` Andreas Grünbacher 2015-04-24 11:04 ` [RFC v3 43/45] uapi/nfs: Add NFSv4.1 ACL definitions Andreas Gruenbacher 2015-05-29 14:57 ` J. Bruce Fields 2015-04-24 11:04 ` [RFC v3 44/45] nfsd: Add support for the v4.1 dacl attribute Andreas Gruenbacher 2015-04-24 11:04 ` [RFC v3 45/45] nfs: " Andreas Gruenbacher 2015-05-23 15:50 ` [RFC v3 00/45] Richacls Jeremy Allison 2015-05-23 15:50 ` Jeremy Allison 2015-05-23 15:56 ` Andreas Grünbacher 2015-05-23 15:56 ` Andreas Grünbacher 2015-06-25 20:03 ` Stefan (metze) Metzmacher
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='0b2401d08da6$dad0d0f0$907272d0$@mindspring.com' \ --to=ffilzlnx@mindspring.com \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.