On Tue, Sep 06, 2011 at 07:28:51PM +0530, Aneesh Kumar K.V wrote: > On Tue, 06 Sep 2011 10:41:06 +0100, Steven Whitehouse <swhiteho@xxxxxxxxxx> wrote: > > Hi, > > > > On Mon, 2011-09-05 at 22:55 +0530, Aneesh Kumar K.V wrote: > > > Hi, > > > > > > The following set of patches implements VFS and ext4 changes needed to implement > > > a new acl model for linux. Rich ACLs are an implementation of NFSv4 ACLs, > > > extended by file masks to fit into the standard POSIX file permission model. > > > They are designed to work seamlessly locally as well as across the NFSv4 and > > > CIFS/SMB2 network file system protocols. > > > > > > A user-space utility for displaying and changing richacls is available at [4] > > > (a number of examples can be found at http://acl.bestbits.at/richacl/examples.html). > > > > > > [4] git://git.kernel.org/pub/scm/fs/acl/kvaneesh/richacl.git master > > > > > > To test richacl on ext4 use -o richacl mount option. This mount option may later be > > > dropped in favour of a feature flag. > > > > > > More details regarding richacl can be found at > > > http://acl.bestbits.at/richacl/ > > > > > > Changes from v5: > > > a) rebase to v3.1-rc4-131-g9e79e3e > > > > > > NOTE: The kernel changes will be pushed to > > > git://git.kernel.org/pub/scm/linux/kernel/git/kvaneesh/linux-richacl.git richacl > > > when kernel.org is back > > > > > > -aneesh > > > > > > > This looks like a really nice patch set. One question though is whether > > there are any test suites which can be used to gain confidence in the > > implementation? Obviously there is a fair amount of change here which > > has security implications, so it would be good to have some test results > > to go along with the patches, > > You can find the tests at > > http://git.kernel.org/?p=fs/acl/kvaneesh/richacl.git;a=tree;f=test;h=3bedf00ac69c79ae7a433996e729d4afb366b229;hb=HEAD Do you have a copy of that anywhere else? gitweb on kernel.org seems to be out at the moment. --b. -- 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
