linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Dave Chinner <david@fromorbit.com>
Cc: agruen@kernel.org, bfields@fieldses.org,
	akpm@linux-foundation.org, viro@zeniv.linux.org.uk,
	dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -V1 19/22] vfs: Cache richacl in struct inode
Date: Thu, 01 May 2014 21:15:11 +0530	[thread overview]
Message-ID: <87a9b1bj08.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140429005203.GT15995@dastard>

Dave Chinner <david@fromorbit.com> writes:

> On Sun, Apr 27, 2014 at 09:44:50PM +0530, Aneesh Kumar K.V wrote:
>> From: Andreas Gruenbacher <agruen@kernel.org>
>> 
>> Cache richacls in struct inode so that this doesn't have to be done
>> individually in each filesystem.
>> 
>> Signed-off-by: Andreas Gruenbacher <agruen@kernel.org>
>> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
>> ---
>>  fs/inode.c              | 25 ++++++++++++++++++-----
>>  include/linux/fs.h      | 12 +++++++++--
>>  include/linux/richacl.h | 53 +++++++++++++++++++++++++++++++++++++++++++++++++
>>  3 files changed, 83 insertions(+), 7 deletions(-)
>> 
>> diff --git a/fs/inode.c b/fs/inode.c
>> index f96d2a6f88cc..b96a16d5c653 100644
>> --- a/fs/inode.c
>> +++ b/fs/inode.c
>> @@ -18,6 +18,7 @@
>>  #include <linux/buffer_head.h> /* for inode_has_buffers */
>>  #include <linux/ratelimit.h>
>>  #include <linux/list_lru.h>
>> +#include <linux/richacl.h>
>>  #include "internal.h"
>>  
>>  /*
>> @@ -185,7 +186,12 @@ int inode_init_always(struct super_block *sb, struct inode *inode)
>>  	inode->i_mapping = mapping;
>>  	INIT_HLIST_HEAD(&inode->i_dentry);	/* buggered by rcu freeing */
>>  #ifdef CONFIG_FS_POSIX_ACL
>> -	inode->i_acl = inode->i_default_acl = ACL_NOT_CACHED;
>> +	if (IS_POSIXACL(inode))
>> +		inode->i_acl = inode->i_default_acl = ACL_NOT_CACHED;
>> +#endif
>> +#ifdef CONFIG_FS_RICHACL
>> +	if (IS_RICHACL(inode))
>> +		inode->i_richacl = ACL_NOT_CACHED;
>>  #endif
>
> That's just plain wrong. i think this is what Christoph didn't like.
> An inode can have either a POSIX ACL or a RICH ACL, so there is no
> need for multiple pointers in the inode for them.

We don't really have multiple pointers

	union {
#ifdef CONFIG_FS_POSIX_ACL
		struct {
			struct posix_acl *i_acl;
			struct posix_acl *i_default_acl;
		};
#endif
#ifdef CONFIG_FS_RICHACL
		struct richacl	*i_richacl;
#endif
	};


But I understand what you are suggesting here. Will try to rework and
see how much easy/simpler it makes the code. 

>
>>  
>>  #ifdef CONFIG_FSNOTIFY
>> @@ -240,10 +246,19 @@ void __destroy_inode(struct inode *inode)
>>  	}
>>  
>>  #ifdef CONFIG_FS_POSIX_ACL
>> -	if (inode->i_acl && inode->i_acl != ACL_NOT_CACHED)
>> -		posix_acl_release(inode->i_acl);
>> -	if (inode->i_default_acl && inode->i_default_acl != ACL_NOT_CACHED)
>> -		posix_acl_release(inode->i_default_acl);
>> +	if (IS_POSIXACL(inode)) {
>> +		if (inode->i_acl && inode->i_acl != ACL_NOT_CACHED)
>> +			posix_acl_release(inode->i_acl);
>> +		if (inode->i_default_acl &&
>> +		    inode->i_default_acl != ACL_NOT_CACHED)
>> +			posix_acl_release(inode->i_default_acl);
>> +	}
>> +#endif
>> +#ifdef CONFIG_FS_RICHACL
>> +	if (IS_RICHACL(inode)) {
>> +		if (inode->i_richacl && inode->i_richacl != ACL_NOT_CACHED)
>> +			richacl_put(inode->i_richacl);
>> +	}
>>  #endif
>
> 	if (inode->i_acl && inode->i_acl != ACL_NOT_CACHED)
> 		acl_release(inode->i_acl);
>
> And all the mess of working out what acl needs releasing get taken
> out of of this code.

Understood. Will try to see how much I can simplify.

>
>> index 22d85798b520..95df64d21e55 100644
>> --- a/include/linux/fs.h
>> +++ b/include/linux/fs.h
>> @@ -492,6 +492,7 @@ static inline int mapping_writably_mapped(struct address_space *mapping)
>>  #endif
>>  
>>  struct posix_acl;
>> +struct richacl;
>>  #define ACL_NOT_CACHED ((void *)(-1))
>>  
>>  #define IOP_FASTPERM	0x0001
>> @@ -510,10 +511,17 @@ struct inode {
>>  	kgid_t			i_gid;
>>  	unsigned int		i_flags;
>>  
>> +	union {
>>  #ifdef CONFIG_FS_POSIX_ACL
>> -	struct posix_acl	*i_acl;
>> -	struct posix_acl	*i_default_acl;
>> +		struct {
>> +			struct posix_acl *i_acl;
>> +			struct posix_acl *i_default_acl;
>> +		};
>>  #endif
>> +#ifdef CONFIG_FS_RICHACL
>> +		struct richacl	*i_richacl;
>> +#endif
>> +	};
>
>>  
>>  	const struct inode_operations	*i_op;
>>  	struct super_block	*i_sb;
>> diff --git a/include/linux/richacl.h b/include/linux/richacl.h
>> index 88f95d78b897..a7db341e4ee9 100644
>> --- a/include/linux/richacl.h
>> +++ b/include/linux/richacl.h
>> @@ -191,6 +191,59 @@ richacl_put(struct richacl *acl)
>>  		kfree(acl);
>>  }
>>  
>> +#ifdef CONFIG_FS_RICHACL
>> +static inline struct richacl *get_cached_richacl(struct inode *inode)
>> +{
>> +	struct richacl **p, *acl;
>> +
>> +	p = &inode->i_richacl;
>> +	acl = ACCESS_ONCE(*p);
>> +	if (acl) {
>> +		spin_lock(&inode->i_lock);
>> +		acl = *p;
>> +		if (acl != ACL_NOT_CACHED)
>> +			acl = richacl_get(acl);
>> +		spin_unlock(&inode->i_lock);
>> +	}
>> +	return acl;
>> +}
>> +
>> +static inline void set_cached_richacl(struct inode *inode,
>> +				      struct richacl *acl)
>> +{
>> +	struct richacl *old = NULL;
>> +	spin_lock(&inode->i_lock);
>> +	old = inode->i_richacl;
>> +	inode->i_richacl = richacl_get(acl);
>> +	spin_unlock(&inode->i_lock);
>> +	if (old != ACL_NOT_CACHED)
>> +		richacl_put(old);
>> +}
>> +
>> +static inline void forget_cached_richacl(struct inode *inode)
>> +{
>> +	struct richacl *old = NULL;
>> +	spin_lock(&inode->i_lock);
>> +	old = inode->i_richacl;
>> +	inode->i_richacl = ACL_NOT_CACHED;
>> +	spin_unlock(&inode->i_lock);
>> +	if (old != ACL_NOT_CACHED)
>> +		richacl_put(old);
>> +}
>> +
>> +static inline int negative_cached_richacl(struct inode *inode)
>> +{
>> +	struct richacl **p, *acl;
>> +
>> +	p = &inode->i_richacl;
>> +	acl = ACCESS_ONCE(*p);
>> +	if (acl)
>> +		return 0;
>> +	return 1;
>> +}
>> +
>> +#endif
>
> This is all just copy-and-paste from the posix_acl code with the RCU
> path-walk awareness removed from it. There should only be a single
> RCU aware version of these functions that does not care what type of
> ACL is in use.
>

Ok.

-aneesh


  parent reply	other threads:[~2014-05-01 15:45 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-27 16:14 [PATCH -V1 00/22] New ACL format for better NFSv4 acl interoperability Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 01/22] vfs: Add generic IS_ACL() test for acl support Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 02/22] vfs: Add IS_RICHACL() test for richacl support Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 03/22] vfs: Optimize out IS_RICHACL() if CONFIG_FS_RICHACL is not defined Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 04/22] vfs: check for directory early Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 05/22] vfs: Add new file and directory create permission flags Aneesh Kumar K.V
2014-04-28 11:23   ` Jeff Layton
2014-04-29  0:04     ` Dave Chinner
2014-05-01 15:16       ` Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 06/22] vfs: Add delete child and delete self " Aneesh Kumar K.V
2014-04-29  0:07   ` Dave Chinner
2014-05-01 15:18     ` Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 07/22] vfs: Make the inode passed to inode_change_ok non-const Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 08/22] vfs: Add permission flags for setting file attributes Aneesh Kumar K.V
2014-04-29  0:17   ` Dave Chinner
2014-05-01 15:20     ` Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 09/22] vfs: Make acl_permission_check() work for richacls Aneesh Kumar K.V
2014-04-29  0:20   ` Dave Chinner
2014-05-01 15:39     ` Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 10/22] richacl: In-memory representation and helper functions Aneesh Kumar K.V
2014-04-29  0:24   ` Dave Chinner
2014-05-01 15:42     ` Aneesh Kumar K.V
2014-05-06  9:35   ` Kinglong Mee
2014-04-27 16:14 ` [PATCH -V1 11/22] richacl: Permission mapping functions Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 12/22] richacl: Compute maximum file masks from an acl Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 13/22] richacl: Update the file masks in chmod() Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 14/22] richacl: Permission check algorithm Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 15/22] richacl: Create-time inheritance Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 16/22] richacl: Check if an acl is equivalent to a file mode Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 17/22] richacl: Automatic Inheritance Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 18/22] richacl: xattr mapping functions Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 19/22] vfs: Cache richacl in struct inode Aneesh Kumar K.V
2014-04-29  0:52   ` Dave Chinner
2014-04-29 12:16     ` Matthew Wilcox
2014-05-01 15:45     ` Aneesh Kumar K.V [this message]
2014-04-27 16:14 ` [PATCH -V1 20/22] vfs: Add richacl permission check Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 21/22] ext4: Implement rich acl for ext4 Aneesh Kumar K.V
2014-04-27 16:14 ` [PATCH -V1 22/22] ext4: Add Ext4 compat richacl feature flag Aneesh Kumar K.V
2014-04-28 21:31   ` Andreas Dilger
2014-05-01 15:48     ` Aneesh Kumar K.V
2014-05-01 17:52       ` Andreas Dilger
2014-04-27 22:20 ` [PATCH -V1 00/22] New ACL format for better NFSv4 acl interoperability Dave Chinner
2014-04-28  5:24   ` Aneesh Kumar K.V
2014-04-28 23:58     ` Dave Chinner
2014-05-01 15:49       ` Aneesh Kumar K.V
2014-04-28  4:39 ` Christoph Hellwig
2014-04-28  5:54   ` Aneesh Kumar K.V
2014-04-28  9:03     ` Christoph Hellwig
2014-05-06 20:15 ` J. Bruce Fields

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=87a9b1bj08.fsf@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=agruen@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --cc=david@fromorbit.com \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).