On Wed, 7 Sep 2011 17:50:22 -0400, "J. Bruce Fields" <bfields@xxxxxxxxxxxx> wrote: > On Mon, Sep 05, 2011 at 10:55:39PM +0530, Aneesh Kumar K.V wrote: > > From: Andreas Gruenbacher <agruen@xxxxxxxxxx> > > > > As in the standard POSIX file permission model, each process is the > > owner, group, or other file class. A process is > > > > - in the owner file class if it owns the file, > > - in the group file class if it is in the file's owning group or it > > matches any of the user or group entries, and > > - in the other file class otherwise. > > > > Each file class is associated with a file mask. > > > > A richacl grants a requested access if the NFSv4 acl in the richacl > > grants the requested permissions (according to the NFSv4 permission > > check algorithm) and the file mask that applies to the process includes > > the requested permissions. > > I assume that by default any ui normally recalculates an upper-bound > mask automatically when you add an ace, as the posix setfacl does, so > the user doesn't have to think about masks too much? > yes. richacl userspace command does this. -aneesh -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
