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, Andreas Gruenbacher <agruen@kernel.org> Subject: Re: [RFC v3 29/45] richacl: Apply the file masks to a richacl Date: Tue, 26 May 2015 17:56:49 -0400 [thread overview] Message-ID: <20150526215649.GA13524@fieldses.org> (raw) In-Reply-To: <35b73e9515f2395c8595cbbf4ea7b92216e5e2a0.1429868795.git.agruenba@redhat.com> On Fri, Apr 24, 2015 at 01:04:26PM +0200, Andreas Gruenbacher wrote: > Put all the pieces of the acl transformation puzzle together for > computing a richacl which has the file masks "applied" so that the > standard nfsv4 access check algorithm can be used on the richacl. > > Signed-off-by: Andreas Gruenbacher <agruen@kernel.org> > --- > fs/richacl_compat.c | 103 ++++++++++++++++++++++++++++++++++++++++++++++++ > include/linux/richacl.h | 3 ++ > 2 files changed, 106 insertions(+) > > diff --git a/fs/richacl_compat.c b/fs/richacl_compat.c > index 645917f..49af600 100644 > --- a/fs/richacl_compat.c > +++ b/fs/richacl_compat.c > @@ -647,3 +647,106 @@ richacl_isolate_group_class(struct richacl_alloc *x) > } > return 0; > } > + > +/** > + * __richacl_apply_masks - apply the file masks to all aces > + * @x: acl and number of allocated entries > + * > + * Apply the owner mask to owner@ aces, the other mask to > + * everyone@ aces, and the group mask to all other aces. > + * > + * The previous transformations have brought the acl into a > + * form in which applying the masks will not lead to the > + * accidental loss of permissions anymore. > + */ > +static int > +__richacl_apply_masks(struct richacl_alloc *x) > +{ > + struct richace *ace; > + > + richacl_for_each_entry(ace, x->acl) { > + unsigned int mask; > + > + if (richace_is_inherit_only(ace) || !richace_is_allow(ace)) > + continue; > + if (richace_is_owner(ace)) > + mask = x->acl->a_owner_mask; > + else if (richace_is_everyone(ace)) > + mask = x->acl->a_other_mask; > + else > + mask = x->acl->a_group_mask; > + if (richace_change_mask(x, &ace, ace->e_mask & mask)) > + return -1; > + } > + return 0; > +} > + > +/** > + * richacl_apply_masks - apply the masks to the acl > + * > + * Transform @acl so that the standard NFSv4 permission check algorithm (which > + * is not aware of file masks) will compute the same access decisions as the > + * richacl permission check algorithm (which looks at the acl and the file > + * masks). > + * > + * This algorithm is split into several steps: > + * > + * - Move everyone@ aces to the end of the acl. This simplifies the other > + * transformations, and allows the everyone@ allow ace at the end of the > + * acl to eventually allow permissions to the other class only. > + * > + * - Propagate everyone@ permissions up the acl. This transformation makes > + * sure that the owner and group class aces won't lose any permissions when > + * we apply the other mask to the everyone@ allow ace at the end of the acl. > + * > + * - Apply the file masks to all aces. > + * > + * - Make sure that the owner is not granted any permissions beyond the owner > + * mask from group class aces or from everyone@. > + * > + * - Make sure that the group class is not granted any permissions from > + * everyone@. > + * > + * The algorithm is exact except for richacls which cannot be represented as an > + * acl alone: for example, given this acl: > + * > + * group@:rw::allow > + * > + * when file masks corresponding to mode 0600 are applied, the owner would only > + * get rw access if he is a member of the owning group. This algorithm would > + * produce an empty acl in this case. We fix this case by modifying > + * richacl_permission() so that the group mask is always applied to group class > + * aces. With this fix, the owner would not have any access (beyond the > + * implicit permissions always granted to owners). This discussion is really confusing. If I understand correctly, you're saying: - this mapping is inaccurate in some cases. - therefore we've modified the permission algorithm to fix those cases. - therefore actually, wait, the mapping is always accurate. Do I have this right? Please just define the group-mask behavior to be part of the richacl permission-checking algorithm from the start, and this will be less confusing. I don't think I'm convinced yet that the resulting algorithm really is correct. I mean: I think it probably is, I just don't understand the argument quite yet. > + * > + * NOTE: Depending on the acl and file masks, this algorithm can increase the > + * number of aces by almost a factor of three in the worst case. This may make > + * the acl too large for some purposes. If only for the sake of reviewers, it would be helpful to have some more detail here to convince us that this isn't going to be a big problem in practice. For example, can we identify a subset of richacls which would cover most reasonable use cases and not be badly mangled by this algorithm? It would be nice to be able to document some simple best practices which if followed would guarantee that the mapped acls will be sane. (Order denies before allows? Stick to a single EVERYONE@ ace at the end? Don't chmod to modes which give more permissions to other than to the group or to the group than to the owner?). --b. > + */ > +int > +richacl_apply_masks(struct richacl **acl) > +{ > + if ((*acl)->a_flags & RICHACL_MASKED) { > + struct richacl_alloc x = { > + .acl = richacl_clone(*acl, GFP_KERNEL), > + .count = (*acl)->a_count, > + }; > + if (!x.acl) > + return -ENOMEM; > + > + if (richacl_move_everyone_aces_down(&x) || > + richacl_propagate_everyone(&x) || > + __richacl_apply_masks(&x) || > + richacl_isolate_owner_class(&x) || > + richacl_isolate_group_class(&x)) { > + richacl_put(x.acl); > + return -ENOMEM; > + } > + > + x.acl->a_flags &= ~RICHACL_MASKED; > + richacl_put(*acl); > + *acl = x.acl; > + } > + return 0; > +} > +EXPORT_SYMBOL_GPL(richacl_apply_masks); > diff --git a/include/linux/richacl.h b/include/linux/richacl.h > index bcc2b64..6a97dca 100644 > --- a/include/linux/richacl.h > +++ b/include/linux/richacl.h > @@ -325,4 +325,7 @@ extern int richacl_equiv_mode(const struct richacl *, mode_t *); > extern int richacl_permission(struct inode *, const struct richacl *, int); > extern struct richacl *richacl_create(struct inode *, struct inode *); > > +/* richacl_compat.c */ > +extern int richacl_apply_masks(struct richacl **); > + > #endif /* __RICHACL_H */ > -- > 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: bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org (J. Bruce Fields) To: Andreas Gruenbacher <andreas.gruenbacher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Andreas Gruenbacher <agruen-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> Subject: Re: [RFC v3 29/45] richacl: Apply the file masks to a richacl Date: Tue, 26 May 2015 17:56:49 -0400 [thread overview] Message-ID: <20150526215649.GA13524@fieldses.org> (raw) In-Reply-To: <35b73e9515f2395c8595cbbf4ea7b92216e5e2a0.1429868795.git.agruenba-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> On Fri, Apr 24, 2015 at 01:04:26PM +0200, Andreas Gruenbacher wrote: > Put all the pieces of the acl transformation puzzle together for > computing a richacl which has the file masks "applied" so that the > standard nfsv4 access check algorithm can be used on the richacl. > > Signed-off-by: Andreas Gruenbacher <agruen-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> > --- > fs/richacl_compat.c | 103 ++++++++++++++++++++++++++++++++++++++++++++++++ > include/linux/richacl.h | 3 ++ > 2 files changed, 106 insertions(+) > > diff --git a/fs/richacl_compat.c b/fs/richacl_compat.c > index 645917f..49af600 100644 > --- a/fs/richacl_compat.c > +++ b/fs/richacl_compat.c > @@ -647,3 +647,106 @@ richacl_isolate_group_class(struct richacl_alloc *x) > } > return 0; > } > + > +/** > + * __richacl_apply_masks - apply the file masks to all aces > + * @x: acl and number of allocated entries > + * > + * Apply the owner mask to owner@ aces, the other mask to > + * everyone@ aces, and the group mask to all other aces. > + * > + * The previous transformations have brought the acl into a > + * form in which applying the masks will not lead to the > + * accidental loss of permissions anymore. > + */ > +static int > +__richacl_apply_masks(struct richacl_alloc *x) > +{ > + struct richace *ace; > + > + richacl_for_each_entry(ace, x->acl) { > + unsigned int mask; > + > + if (richace_is_inherit_only(ace) || !richace_is_allow(ace)) > + continue; > + if (richace_is_owner(ace)) > + mask = x->acl->a_owner_mask; > + else if (richace_is_everyone(ace)) > + mask = x->acl->a_other_mask; > + else > + mask = x->acl->a_group_mask; > + if (richace_change_mask(x, &ace, ace->e_mask & mask)) > + return -1; > + } > + return 0; > +} > + > +/** > + * richacl_apply_masks - apply the masks to the acl > + * > + * Transform @acl so that the standard NFSv4 permission check algorithm (which > + * is not aware of file masks) will compute the same access decisions as the > + * richacl permission check algorithm (which looks at the acl and the file > + * masks). > + * > + * This algorithm is split into several steps: > + * > + * - Move everyone@ aces to the end of the acl. This simplifies the other > + * transformations, and allows the everyone@ allow ace at the end of the > + * acl to eventually allow permissions to the other class only. > + * > + * - Propagate everyone@ permissions up the acl. This transformation makes > + * sure that the owner and group class aces won't lose any permissions when > + * we apply the other mask to the everyone@ allow ace at the end of the acl. > + * > + * - Apply the file masks to all aces. > + * > + * - Make sure that the owner is not granted any permissions beyond the owner > + * mask from group class aces or from everyone@. > + * > + * - Make sure that the group class is not granted any permissions from > + * everyone@. > + * > + * The algorithm is exact except for richacls which cannot be represented as an > + * acl alone: for example, given this acl: > + * > + * group@:rw::allow > + * > + * when file masks corresponding to mode 0600 are applied, the owner would only > + * get rw access if he is a member of the owning group. This algorithm would > + * produce an empty acl in this case. We fix this case by modifying > + * richacl_permission() so that the group mask is always applied to group class > + * aces. With this fix, the owner would not have any access (beyond the > + * implicit permissions always granted to owners). This discussion is really confusing. If I understand correctly, you're saying: - this mapping is inaccurate in some cases. - therefore we've modified the permission algorithm to fix those cases. - therefore actually, wait, the mapping is always accurate. Do I have this right? Please just define the group-mask behavior to be part of the richacl permission-checking algorithm from the start, and this will be less confusing. I don't think I'm convinced yet that the resulting algorithm really is correct. I mean: I think it probably is, I just don't understand the argument quite yet. > + * > + * NOTE: Depending on the acl and file masks, this algorithm can increase the > + * number of aces by almost a factor of three in the worst case. This may make > + * the acl too large for some purposes. If only for the sake of reviewers, it would be helpful to have some more detail here to convince us that this isn't going to be a big problem in practice. For example, can we identify a subset of richacls which would cover most reasonable use cases and not be badly mangled by this algorithm? It would be nice to be able to document some simple best practices which if followed would guarantee that the mapped acls will be sane. (Order denies before allows? Stick to a single EVERYONE@ ace at the end? Don't chmod to modes which give more permissions to other than to the group or to the group than to the owner?). --b. > + */ > +int > +richacl_apply_masks(struct richacl **acl) > +{ > + if ((*acl)->a_flags & RICHACL_MASKED) { > + struct richacl_alloc x = { > + .acl = richacl_clone(*acl, GFP_KERNEL), > + .count = (*acl)->a_count, > + }; > + if (!x.acl) > + return -ENOMEM; > + > + if (richacl_move_everyone_aces_down(&x) || > + richacl_propagate_everyone(&x) || > + __richacl_apply_masks(&x) || > + richacl_isolate_owner_class(&x) || > + richacl_isolate_group_class(&x)) { > + richacl_put(x.acl); > + return -ENOMEM; > + } > + > + x.acl->a_flags &= ~RICHACL_MASKED; > + richacl_put(*acl); > + *acl = x.acl; > + } > + return 0; > +} > +EXPORT_SYMBOL_GPL(richacl_apply_masks); > diff --git a/include/linux/richacl.h b/include/linux/richacl.h > index bcc2b64..6a97dca 100644 > --- a/include/linux/richacl.h > +++ b/include/linux/richacl.h > @@ -325,4 +325,7 @@ extern int richacl_equiv_mode(const struct richacl *, mode_t *); > extern int richacl_permission(struct inode *, const struct richacl *, int); > extern struct richacl *richacl_create(struct inode *, struct inode *); > > +/* richacl_compat.c */ > +extern int richacl_apply_masks(struct richacl **); > + > #endif /* __RICHACL_H */ > -- > 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-26 21:56 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 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 [this message] 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=20150526215649.GA13524@fieldses.org \ --to=bfields@fieldses.org \ --cc=agruen@kernel.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: 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.