From: Coywolf Qi Hunt <qiyong@fc-cn.com>
To: Neil Brown <neilb@suse.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: [patch 1/2] raid6_end_write_request() spinlock fix
Date: Tue, 25 Apr 2006 14:43:10 +0800 [thread overview]
Message-ID: <20060425064310.GA29950@localhost.localdomain> (raw)
In-Reply-To: <17485.45069.692725.551853@cse.unsw.edu.au>
On Tue, Apr 25, 2006 at 03:13:49PM +1000, Neil Brown wrote:
> On Tuesday April 25, qiyong@fc-cn.com wrote:
> > Hello,
> >
> > Reduce the raid6_end_write_request() spinlock window.
>
> Andrew: please don't include these in -mm. This one and the
> corresponding raid5 are wrong, and I'm not sure yet the unplug_device
> changes.
I am sure with the unplug_device. Just look follow the path...
>
> In this case, the call to md_error, which in turn calls "error" in
> raid6main.c, requires the lock to be held as it contains:
> if (!test_bit(Faulty, &rdev->flags)) {
> mddev->sb_dirty = 1;
> if (test_bit(In_sync, &rdev->flags)) {
> conf->working_disks--;
> mddev->degraded++;
> conf->failed_disks++;
> clear_bit(In_sync, &rdev->flags);
> /*
> * if recovery was running, make sure it aborts.
> */
> set_bit(MD_RECOVERY_ERR, &mddev->recovery);
> }
> set_bit(Faulty, &rdev->flags);
>
> which is fairly clearly not safe without some locking.
Yes. Let's fix the error(). In any case, the current code is broken. (see raid5/6_end_read_request)
Comments? Thanks.
Signed-off-by: Coywolf Qi Hunt <qiyong@fc-cn.com>
---
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index 9c24377..192de19 100644
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c
@@ -638,7 +638,7 @@ static void error(mddev_t *mddev, mdk_rd
raid5_conf_t *conf = (raid5_conf_t *) mddev->private;
PRINTK("raid5: error called\n");
- if (!test_bit(Faulty, &rdev->flags)) {
+ if (!test_and_set_bit(Faulty, &rdev->flags)) {
mddev->sb_dirty = 1;
if (test_bit(In_sync, &rdev->flags)) {
conf->working_disks--;
@@ -650,7 +650,6 @@ static void error(mddev_t *mddev, mdk_rd
*/
set_bit(MD_RECOVERY_ERR, &mddev->recovery);
}
- set_bit(Faulty, &rdev->flags);
printk (KERN_ALERT
"raid5: Disk failure on %s, disabling device."
" Operation continuing on %d devices\n",
diff --git a/drivers/md/raid6main.c b/drivers/md/raid6main.c
index d3deedb..fc0b31d 100644
--- a/drivers/md/raid6main.c
+++ b/drivers/md/raid6main.c
@@ -527,7 +527,7 @@ static void error(mddev_t *mddev, mdk_rd
raid6_conf_t *conf = (raid6_conf_t *) mddev->private;
PRINTK("raid6: error called\n");
- if (!test_bit(Faulty, &rdev->flags)) {
+ if (!test_and_set_bit(Faulty, &rdev->flags)) {
mddev->sb_dirty = 1;
if (test_bit(In_sync, &rdev->flags)) {
conf->working_disks--;
@@ -539,7 +539,6 @@ static void error(mddev_t *mddev, mdk_rd
*/
set_bit(MD_RECOVERY_ERR, &mddev->recovery);
}
- set_bit(Faulty, &rdev->flags);
printk (KERN_ALERT
"raid6: Disk failure on %s, disabling device."
" Operation continuing on %d devices\n",
>
> Coywolf: As I think I have already said, I appreciate your review of
> the md/raid code and your attempts to improve it - I'm sure there is
> plenty of room to make improvements.
> However posting patches with minimal commentary on code that you don't
> fully understand is not the best way to work with the community.
> If you see something that you think is wrong, it is much better to ask
> why it is the way it is, explain why you think it isn't right, and
> quite possibly include an example patch. Then we can discuss the
> issue and find the best solution.
>
> So please feel free to post further patches, but please include more
> commentary, and don't assume you understand something that you don't
> really.
>
> Thanks,
> NeilBrown
>
>
>
> >
> > Signed-off-by: Coywolf Qi Hunt <qiyong@fc-cn.com>
> > ---
> >
> > diff --git a/drivers/md/raid6main.c b/drivers/md/raid6main.c
> > index bc69355..820536e 100644
> > --- a/drivers/md/raid6main.c
> > +++ b/drivers/md/raid6main.c
> > @@ -468,7 +468,6 @@ static int raid6_end_write_request (stru
> > struct stripe_head *sh = bi->bi_private;
> > raid6_conf_t *conf = sh->raid_conf;
> > int disks = conf->raid_disks, i;
> > - unsigned long flags;
> > int uptodate = test_bit(BIO_UPTODATE, &bi->bi_flags);
> >
> > if (bi->bi_size)
> > @@ -486,16 +485,14 @@ static int raid6_end_write_request (stru
> > return 0;
> > }
> >
> > - spin_lock_irqsave(&conf->device_lock, flags);
> > if (!uptodate)
> > md_error(conf->mddev, conf->disks[i].rdev);
> >
> > rdev_dec_pending(conf->disks[i].rdev, conf->mddev);
> > -
> > clear_bit(R5_LOCKED, &sh->dev[i].flags);
> > set_bit(STRIPE_HANDLE, &sh->state);
> > - __release_stripe(conf, sh);
> > - spin_unlock_irqrestore(&conf->device_lock, flags);
> > + release_stripe(sh);
> > +
> > return 0;
> > }
> >
--
Coywolf Qi Hunt
next prev parent reply other threads:[~2006-04-25 6:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 3:35 [patch 1/2] raid6_end_write_request() spinlock fix Coywolf Qi Hunt
2006-04-25 5:13 ` Neil Brown
2006-04-25 6:43 ` Coywolf Qi Hunt [this message]
2006-04-25 6:50 ` Neil Brown
2006-04-25 8:07 ` Coywolf Qi Hunt
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=20060425064310.GA29950@localhost.localdomain \
--to=qiyong@fc-cn.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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.