Re: [PATCH v18 11/22] vfs: Cache base_acl objects in inodes

2016-03-18 Thread Andreas Gruenbacher
On Tue, Mar 15, 2016 at 8:12 AM, Christoph Hellwig wrote: > On Fri, Mar 11, 2016 at 05:24:45PM +0100, Andreas Gruenbacher wrote: >> POSIX ACLs and RichACLs are different objects, with different members >> and different algorithms operating on them. The only commonality is >> that they are both kma

Re: [PATCH v18 11/22] vfs: Cache base_acl objects in inodes

2016-03-15 Thread Christoph Hellwig
On Fri, Mar 11, 2016 at 05:24:45PM +0100, Andreas Gruenbacher wrote: > POSIX ACLs and RichACLs are different objects, with different members > and different algorithms operating on them. The only commonality is > that they are both kmalloc()ed, reference counted objects, and when an > inode is dest

Re: [PATCH v18 11/22] vfs: Cache base_acl objects in inodes

2016-03-11 Thread Andreas Gruenbacher
On Fri, Mar 11, 2016 at 3:07 PM, Christoph Hellwig wrote: > On Mon, Feb 29, 2016 at 09:17:16AM +0100, Andreas Gruenbacher wrote: >> POSIX ACLs and richacls are both objects allocated by kmalloc() with a >> reference count which are freed by kfree_rcu(). An inode can either >> cache an access and

Re: [PATCH v18 11/22] vfs: Cache base_acl objects in inodes

2016-03-11 Thread Christoph Hellwig
On Mon, Feb 29, 2016 at 09:17:16AM +0100, Andreas Gruenbacher wrote: > POSIX ACLs and richacls are both objects allocated by kmalloc() with a > reference count which are freed by kfree_rcu(). An inode can either > cache an access and a default POSIX ACL, or a richacl (richacls do not > have defaul

[PATCH v18 11/22] vfs: Cache base_acl objects in inodes

2016-02-29 Thread Andreas Gruenbacher
POSIX ACLs and richacls are both objects allocated by kmalloc() with a reference count which are freed by kfree_rcu(). An inode can either cache an access and a default POSIX ACL, or a richacl (richacls do not have default acls). To allow an inode to cache either of the two kinds of acls, introdu