linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Shaohua Li <shli@kernel.org>
Cc: linux-raid@vger.kernel.org, maxime.ripard@free-electrons.com
Subject: Re: [PATCH] raid5: fix broken async operation chain
Date: Wed, 20 May 2015 16:14:38 +1000	[thread overview]
Message-ID: <20150520161438.7d982d16@notabene.brown> (raw)
In-Reply-To: <abe8bcda859c8d2a11544a273c117c190fe736a4.1431464773.git.shli@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]

On Wed, 13 May 2015 09:30:08 -0700 Shaohua Li <shli@kernel.org> wrote:

> ops_run_reconstruct6() doesn't correctly chain asyn operations. The tx returned
> by async_gen_syndrome should be added as the dependent tx of next stripe.
> 
> The issue is introduced by commit 59fc630b8b5f9f21c8ce3ba153341c107dce1b0c
>     RAID5: batch adjacent full stripe write
> 
> Reported-and-tested-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> Signed-off-by: Shaohua Li <shli@fb.com>
> ---
>  drivers/md/raid5.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
> index 1ba97fd..b9f2b9c 100644
> --- a/drivers/md/raid5.c
> +++ b/drivers/md/raid5.c
> @@ -1822,7 +1822,7 @@ ops_run_reconstruct6(struct stripe_head *sh, struct raid5_percpu *percpu,
>  	} else
>  		init_async_submit(&submit, 0, tx, NULL, NULL,
>  				  to_addr_conv(sh, percpu, j));
> -	async_gen_syndrome(blocks, 0, count+2, STRIPE_SIZE,  &submit);
> +	tx = async_gen_syndrome(blocks, 0, count+2, STRIPE_SIZE,  &submit);
>  	if (!last_stripe) {
>  		j++;
>  		sh = list_first_entry(&sh->batch_list, struct stripe_head,


applied, thanks.

NeilBrown

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

      reply	other threads:[~2015-05-20  6:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 16:30 [PATCH] raid5: fix broken async operation chain Shaohua Li
2015-05-20  6:14 ` NeilBrown [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=20150520161438.7d982d16@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=shli@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 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).