From: Song Liu <liu.song.a23@gmail.com>
To: Nigel Croxon <ncroxon@redhat.com>
Cc: Vitaly Mayatskikh <vmayatskikh@digitalocean.com>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [PATCH 1/1] md/raid10: avoid deadlock on recovery.
Date: Tue, 21 Jul 2020 23:18:19 -0700 [thread overview]
Message-ID: <CAPhsuW5mSbNNspW2tPy-RZW0MmqZkEfsGzLPh1EvXkzW=eS1vg@mail.gmail.com> (raw)
In-Reply-To: <D5A36675-8344-4D67-9836-64F9BA78D78E@redhat.com>
On Tue, Jul 21, 2020 at 7:26 AM Nigel Croxon <ncroxon@redhat.com> wrote:
>
>
> > On Mar 3, 2020, at 1:14 PM, Vitaly Mayatskikh <vmayatskikh@digitalocean.com> wrote:
> >
> > When disk failure happens and the array has a spare drive, resync thread
> > kicks in and starts to refill the spare. However it may get blocked by
> > a retry thread that resubmits failed IO to a mirror and itself can get
> > blocked on a barrier raised by the resync thread.
> >
> > Signed-off-by: Vitaly Mayatskikh <vmayatskikh@digitalocean.com>
> > ---
> > drivers/md/raid10.c | 14 +++++++++++---
> > 1 file changed, 11 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
> > index ec136e4..f1a8e26 100644
> > --- a/drivers/md/raid10.c
> > +++ b/drivers/md/raid10.c
> > @@ -980,6 +980,7 @@ static void wait_barrier(struct r10conf *conf)
> > {
> > spin_lock_irq(&conf->resync_lock);
> > if (conf->barrier) {
> > + struct bio_list *bio_list = current->bio_list;
> > conf->nr_waiting++;
> > /* Wait for the barrier to drop.
> > * However if there are already pending
> > @@ -994,9 +995,16 @@ static void wait_barrier(struct r10conf *conf)
> > wait_event_lock_irq(conf->wait_barrier,
> > !conf->barrier ||
> > (atomic_read(&conf->nr_pending) &&
> > - current->bio_list &&
> > - (!bio_list_empty(¤t->bio_list[0]) ||
> > - !bio_list_empty(¤t->bio_list[1]))),
> > + bio_list &&
> > + (!bio_list_empty(&bio_list[0]) ||
> > + !bio_list_empty(&bio_list[1]))) ||
> > + /* move on if recovery thread is
> > + * blocked by us
> > + */
> > + (conf->mddev->thread->tsk == current &&
> > + test_bit(MD_RECOVERY_RUNNING,
> > + &conf->mddev->recovery) &&
> > + conf->nr_queued > 0),
> > conf->resync_lock);
> > conf->nr_waiting--;
> > if (!conf->nr_waiting)
> > —
> > 1.8.3.1
> >
>
> Song, Have you had a chance to look at this patch?
> We would like to have it pulled in to the kernel.
I am sorry I missed this one. This looks good to me.
Nigel, would you like to add your Reviewed-by, or Acked-by, or Tested-by tag?
Thanks,
Song
next prev parent reply other threads:[~2020-07-22 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 18:14 [PATCH 0/1] Fix deadlock in raid10 recovery Vitaly Mayatskikh
2020-03-03 18:14 ` [PATCH 1/1] md/raid10: avoid deadlock on recovery Vitaly Mayatskikh
2020-07-21 14:26 ` Nigel Croxon
2020-07-22 6:18 ` Song Liu [this message]
2020-07-22 12:14 ` Nigel Croxon
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='CAPhsuW5mSbNNspW2tPy-RZW0MmqZkEfsGzLPh1EvXkzW=eS1vg@mail.gmail.com' \
--to=liu.song.a23@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=ncroxon@redhat.com \
--cc=vmayatskikh@digitalocean.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;
as well as URLs for NNTP newsgroup(s).