All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/5] Btrfs: remove unnecessary argument of bio_readpage_error()
Date: Thu, 11 Jul 2013 16:05:14 +0800	[thread overview]
Message-ID: <51DE673A.1050100@cn.fujitsu.com> (raw)
In-Reply-To: <1373520339-13870-1-git-send-email-miaox@cn.fujitsu.com>

There are only 4 patches in this patchset, not 5.
Sorry for my mistake.

Miao

On thu, 11 Jul 2013 13:25:36 +0800, Miao Xie wrote:
> Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
> ---
>  fs/btrfs/extent_io.c | 25 +++++++++++--------------
>  1 file changed, 11 insertions(+), 14 deletions(-)
> 
> diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
> index f8586a9..4bfbcc5 100644
> --- a/fs/btrfs/extent_io.c
> +++ b/fs/btrfs/extent_io.c
> @@ -2202,8 +2202,7 @@ out:
>   */
>  
>  static int bio_readpage_error(struct bio *failed_bio, struct page *page,
> -				u64 start, u64 end, int failed_mirror,
> -				struct extent_state *state)
> +				u64 start, u64 end, int failed_mirror)
>  {
>  	struct io_failure_record *failrec = NULL;
>  	u64 private;
> @@ -2212,6 +2211,7 @@ static int bio_readpage_error(struct bio *failed_bio, struct page *page,
>  	struct extent_io_tree *failure_tree = &BTRFS_I(inode)->io_failure_tree;
>  	struct extent_io_tree *tree = &BTRFS_I(inode)->io_tree;
>  	struct extent_map_tree *em_tree = &BTRFS_I(inode)->extent_tree;
> +	struct extent_state *state;
>  	struct bio *bio;
>  	int num_copies;
>  	int ret;
> @@ -2297,21 +2297,18 @@ static int bio_readpage_error(struct bio *failed_bio, struct page *page,
>  		 * matter what the error is, it is very likely to persist.
>  		 */
>  		pr_debug("bio_readpage_error: cannot repair, num_copies == 1. "
> -			 "state=%p, num_copies=%d, next_mirror %d, "
> -			 "failed_mirror %d\n", state, num_copies,
> -			 failrec->this_mirror, failed_mirror);
> +			 "num_copies=%d, next_mirror %d, failed_mirror %d\n", 
> +			 num_copies, failrec->this_mirror, failed_mirror);
>  		free_io_failure(inode, failrec, 0);
>  		return -EIO;
>  	}
>  
> -	if (!state) {
> -		spin_lock(&tree->lock);
> -		state = find_first_extent_bit_state(tree, failrec->start,
> -						    EXTENT_LOCKED);
> -		if (state && state->start != failrec->start)
> -			state = NULL;
> -		spin_unlock(&tree->lock);
> -	}
> +	spin_lock(&tree->lock);
> +	state = find_first_extent_bit_state(tree, failrec->start,
> +					    EXTENT_LOCKED);
> +	if (state && state->start != failrec->start)
> +		state = NULL;
> +	spin_unlock(&tree->lock);
>  
>  	/*
>  	 * there are two premises:
> @@ -2541,7 +2538,7 @@ static void end_bio_extent_readpage(struct bio *bio, int err)
>  			 * can't handle the error it will return -EIO and we
>  			 * remain responsible for that page.
>  			 */
> -			ret = bio_readpage_error(bio, page, start, end, mirror, NULL);
> +			ret = bio_readpage_error(bio, page, start, end, mirror);
>  			if (ret == 0) {
>  				uptodate =
>  					test_bit(BIO_UPTODATE, &bio->bi_flags);
> 


      parent reply	other threads:[~2013-07-11  8:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11  5:25 [PATCH 1/5] Btrfs: remove unnecessary argument of bio_readpage_error() Miao Xie
2013-07-11  5:25 ` [PATCH 2/5] Btrfs: add branch prediction hints in the read page end IO function Miao Xie
2013-07-11 14:31   ` Chris Mason
2013-07-12 22:19     ` David Sterba
2013-07-11  5:25 ` [PATCH 3/5] Btrfs: don't cache the csum value into the extent state tree Miao Xie
2013-07-11 14:29   ` Chris Mason
2013-07-11  5:25 ` [PATCH 4/5] Btrfs: batch the extent state operation in the end io handle of the read page Miao Xie
2013-07-11 18:56   ` Josef Bacik
2013-07-11  8:05 ` Miao Xie [this message]

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=51DE673A.1050100@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.