public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Miao Xie <miaoxie@huawei.com>
To: <linux-ext4@vger.kernel.org>
Cc: <tytso@mit.edu>, <lixi@ddn.com>, <yi.zhang@huawei.com>,
	<adilger@dilger.ca>, <wshilong@ddn.com>, <sihara@ddn.com>
Subject: Re: [PATCH 1/4] ext4: fix forgetten xattr lock protection in ext4_expand_extra_isize
Date: Thu, 13 Jul 2017 20:55:55 +0800	[thread overview]
Message-ID: <e7301611-0fed-fbbf-3ab9-49f2287a14eb@huawei.com> (raw)
In-Reply-To: <1499360993-17130-1-git-send-email-miaoxie@huawei.com>

Ping......

on 2017/7/7 at 1:09, Miao Xie wrote:
> We should avoid the contention between the i_extra_isize update and
> the inline data insertion, so move the xattr trylock in front of
> i_extra_isize update.
> 
> Signed-off-by: Miao Xie <miaoxie@huawei.com>
> Reviewed-by: Wang Shilong <wshilong@ddn.com>
> ---
>  fs/ext4/inode.c | 18 ++++++++++++++++--
>  fs/ext4/xattr.c | 10 ----------
>  2 files changed, 16 insertions(+), 12 deletions(-)
> 
> diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
> index 5cf82d0..4af3edc 100644
> --- a/fs/ext4/inode.c
> +++ b/fs/ext4/inode.c
> @@ -5639,10 +5639,15 @@ static int ext4_expand_extra_isize(struct inode *inode,
>  {
>  	struct ext4_inode *raw_inode;
>  	struct ext4_xattr_ibody_header *header;
> +	int no_expand;
> +	int error;
>  
>  	if (EXT4_I(inode)->i_extra_isize >= new_extra_isize)
>  		return 0;
>  
> +	if (ext4_write_trylock_xattr(inode, &no_expand) == 0)
> +		return 0;
> +
>  	raw_inode = ext4_raw_inode(&iloc);
>  
>  	header = IHDR(inode, raw_inode);
> @@ -5654,12 +5659,21 @@ static int ext4_expand_extra_isize(struct inode *inode,
>  		       EXT4_I(inode)->i_extra_isize, 0,
>  		       new_extra_isize - EXT4_I(inode)->i_extra_isize);
>  		EXT4_I(inode)->i_extra_isize = new_extra_isize;
> +		ext4_write_unlock_xattr(inode, &no_expand);
>  		return 0;
>  	}
>  
>  	/* try to expand with EAs present */
> -	return ext4_expand_extra_isize_ea(inode, new_extra_isize,
> -					  raw_inode, handle);
> +	error = ext4_expand_extra_isize_ea(inode, new_extra_isize,
> +					   raw_inode, handle);
> +	if (error) {
> +		/*
> +		 * Inode size expansion failed; don't try again
> +		 */
> +		no_expand = 1;
> +	}
> +	ext4_write_unlock_xattr(inode, &no_expand);
> +	return error;
>  }
>  
>  /*
> diff --git a/fs/ext4/xattr.c b/fs/ext4/xattr.c
> index 5d3c253..12ee5fb 100644
> --- a/fs/ext4/xattr.c
> +++ b/fs/ext4/xattr.c
> @@ -1472,10 +1472,6 @@ int ext4_expand_extra_isize_ea(struct inode *inode, int new_extra_isize,
>  	int error = 0, tried_min_extra_isize = 0;
>  	int s_min_extra_isize = le16_to_cpu(EXT4_SB(inode->i_sb)->s_es->s_min_extra_isize);
>  	int isize_diff;	/* How much do we need to grow i_extra_isize */
> -	int no_expand;
> -
> -	if (ext4_write_trylock_xattr(inode, &no_expand) == 0)
> -		return 0;
>  
>  retry:
>  	isize_diff = new_extra_isize - EXT4_I(inode)->i_extra_isize;
> @@ -1558,16 +1554,10 @@ int ext4_expand_extra_isize_ea(struct inode *inode, int new_extra_isize,
>  	EXT4_I(inode)->i_extra_isize = new_extra_isize;
>  	brelse(bh);
>  out:
> -	ext4_write_unlock_xattr(inode, &no_expand);
>  	return 0;
>  
>  cleanup:
>  	brelse(bh);
> -	/*
> -	 * Inode size expansion failed; don't try again
> -	 */
> -	no_expand = 1;
> -	ext4_write_unlock_xattr(inode, &no_expand);
>  	return error;
>  }
>  
> 

  parent reply	other threads:[~2017-07-13 12:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 17:09 [PATCH 1/4] ext4: fix forgetten xattr lock protection in ext4_expand_extra_isize Miao Xie
2017-07-06 17:09 ` [PATCH 2/4] ext4: restructure ext4_expand_extra_isize Miao Xie
2017-08-06  4:47   ` Theodore Ts'o
2017-07-06 17:09 ` [PATCH 3/4] ext4: cleanup ext4_expand_extra_isize_ea() Miao Xie
2017-08-06  4:56   ` Theodore Ts'o
2017-07-06 17:09 ` [PATCH 4/4] ext4, project: expand inode extra size if possible Miao Xie
2017-08-06  5:05   ` Theodore Ts'o
2017-07-13 12:55 ` Miao Xie [this message]
2017-07-13 13:04   ` [PATCH 1/4] ext4: fix forgetten xattr lock protection in ext4_expand_extra_isize Wang Shilong
2017-07-13 16:47     ` Theodore Ts'o
2017-08-06  4:28 ` Theodore Ts'o

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=e7301611-0fed-fbbf-3ab9-49f2287a14eb@huawei.com \
    --to=miaoxie@huawei.com \
    --cc=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=lixi@ddn.com \
    --cc=sihara@ddn.com \
    --cc=tytso@mit.edu \
    --cc=wshilong@ddn.com \
    --cc=yi.zhang@huawei.com \
    /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