From: Neil Brown <neilb@suse.de>
To: Arthur Jones <ajones@riverbed.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] md: raid10: wake up frozen array
Date: Fri, 1 Aug 2008 13:03:40 +1000 [thread overview]
Message-ID: <18578.32012.13358.269935@notabene.brown> (raw)
In-Reply-To: message from Arthur Jones on Friday July 25
On Friday July 25, ajones@riverbed.com wrote:
> When rescheduling a bio in raid10, we wake up
> the md thread, but if the array is frozen, this
> will have no effect. This causes the array to
> remain frozen for eternity. We add a wake_up
> to allow the array to de-freeze. This code is
> nearly identical to the raid1 code, which has
> this fix already.
Thanks for this! It is "obviously correct" based on the similarity
with raid1.
It is on its way to Linus.
NeilBrown
>
> Signed-off-by: Arthur Jones <ajones@riverbed.com>
> ---
> drivers/md/raid10.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
> index 159535d..d41bebb 100644
> --- a/drivers/md/raid10.c
> +++ b/drivers/md/raid10.c
> @@ -215,6 +215,9 @@ static void reschedule_retry(r10bio_t *r10_bio)
> conf->nr_queued ++;
> spin_unlock_irqrestore(&conf->device_lock, flags);
>
> + /* wake up frozen array... */
> + wake_up(&conf->wait_barrier);
> +
> md_wakeup_thread(mddev->thread);
> }
>
> --
> 1.5.4.3
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-08-01 3:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 19:03 [PATCH] md: raid10: wake up frozen array Arthur Jones
2008-08-01 3:03 ` Neil Brown [this message]
2008-08-30 21:30 ` Clive Messer
2008-09-02 15:07 ` Arthur Jones
2008-09-05 16:58 ` Bill Davidsen
2008-09-05 17:04 ` Arthur Jones
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=18578.32012.13358.269935@notabene.brown \
--to=neilb@suse.de \
--cc=ajones@riverbed.com \
--cc=linux-raid@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.