From: NeilBrown <neilb@suse.de>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] md/raid5: per hash value and exclusive wait_for_stripe
Date: Thu, 14 May 2015 16:09:15 +1000 [thread overview]
Message-ID: <20150514160915.58dcd4e5@notabene.brown> (raw)
In-Reply-To: <20150514055508.GJ3124@yliu-dev.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1823 bytes --]
On Thu, 14 May 2015 13:55:08 +0800 Yuanhan Liu <yuanhan.liu@linux.intel.com>
wrote:
> On Thu, May 14, 2015 at 03:45:11PM +1000, NeilBrown wrote:
> > On Wed, 29 Apr 2015 10:48:55 +0800 Yuanhan Liu <yuanhan.liu@linux.intel.com>
> > wrote:
> >
> > > diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
> > > index 64d5bea..697d77a 100644
> > > --- a/drivers/md/raid5.c
> > > +++ b/drivers/md/raid5.c
> > > @@ -344,7 +344,8 @@ static void release_inactive_stripe_list(struct r5conf *conf,
> > > int hash)
> > > {
> > > int size;
> > > - bool do_wakeup = false;
> > > + unsigned long do_wakeup = 0;
> > > + int i = 0;
> > > unsigned long flags;
> > >
> > > if (hash == NR_STRIPE_HASH_LOCKS) {
> > > @@ -365,15 +366,19 @@ static void release_inactive_stripe_list(struct r5conf *conf,
> > > !list_empty(list))
> > > atomic_dec(&conf->empty_inactive_list_nr);
> > > list_splice_tail_init(list, conf->inactive_list + hash);
> > > - do_wakeup = true;
> > > + do_wakeup |= 1 << (size - 1);
> > > spin_unlock_irqrestore(conf->hash_locks + hash, flags);
> > > }
> > > size--;
> > > hash--;
> > > }
> > >
> > > + for (i = 0; i < NR_STRIPE_HASH_LOCKS; i++) {
> > > + if (do_wakeup & (1 << i))
> > > + wake_up(&conf->wait_for_stripe[i]);
> > > + }
> > > +
> >
> > hi,
> > I've been doing some testing and got a lock-up in resize_stripes, waiting
> > on wait_for_stripe[].
> >
> > Looking at the above code, I think
> > do_wakeup |= 1 << (size - 1);
> > should be
> > do_wakeup |= 1 << hash;
> >
> > do you agree? Or am I missing something?
>
> Right. Sorry for the careless mistake.
Thanks for confirming.
Mistakes happen - that's why we test :-)
I've merged that fix into your patch.
NeilBrown
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2015-05-14 6:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 2:48 [PATCH 1/3 v2] wait: introduce wait_event_exclusive_cmd Yuanhan Liu
2015-04-29 2:48 ` [PATCH 2/3] md/raid5: split wait_for_stripe and introduce wait_for_quiescent Yuanhan Liu
2015-04-29 2:48 ` [PATCH 3/3] md/raid5: per hash value and exclusive wait_for_stripe Yuanhan Liu
2015-05-14 5:45 ` NeilBrown
2015-05-14 5:55 ` Yuanhan Liu
2015-05-14 6:09 ` NeilBrown [this message]
2015-04-29 9:31 ` [PATCH 1/3 v2] wait: introduce wait_event_exclusive_cmd Peter Zijlstra
2015-04-29 22:17 ` NeilBrown
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=20150514160915.58dcd4e5@notabene.brown \
--to=neilb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=yuanhan.liu@linux.intel.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