The patch titled
md: raid1_quiesce is back to front, fix it.
has been added to the -mm tree. Its filename is
md-raid1_quiesce-is-back-to-front-fix-it.patch
Patches currently in -mm which might be from [EMAIL PROTECTED] are
md-make-sure-resync-gets-started-when-array-starts.patch
sunrpc-cache_register-can-use-wrong-module-reference.patch
md-fix-minor-error-in-raid10-read-balancing-calculation.patch
md-fail-io-request-to-md-that-require-a-barrier.patch
md-dont-allow-new-md-bitmap-file-to-be-set-if-one-already-exists.patch
md-improve-handling-of-bitmap-initialisation.patch
md-all-hot-add-and-hot-remove-of-md-intent-logging-bitmaps.patch
md-support-write-mostly-device-in-raid1.patch
md-add-write-behind-support-for-md-raid1.patch
md-support-md-linear-array-with-components-greater-than-2-terabytes.patch
md-raid1_quiesce-is-back-to-front-fix-it.patch
md-make-sure-bitmap_daemon_work-actually-does-work.patch
md-do-not-set-mddev-bitmap-until-bitmap-is-fully-initialised.patch
md-allow-hot-adding-devices-to-arrays-with-non-persistant-superblocks.patch
md-allow-md-to-load-a-superblock-with-feature-bit-1-set.patch
md-fix-bitmap-read_sb_page-so-that-it-handles-errors-properly.patch
drivers-md-fix-up-schedule_timeout-usage.patch
From: NeilBrown <[EMAIL PROTECTED]>
A state of 0 mean 'not quiesced'
A state of 1 means 'is quiesced'
The original code got this wrong.
Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
drivers/md/raid1.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff -puN drivers/md/raid1.c~md-raid1_quiesce-is-back-to-front-fix-it
drivers/md/raid1.c
--- devel/drivers/md/raid1.c~md-raid1_quiesce-is-back-to-front-fix-it
2005-08-21 22:35:55.000000000 -0700
+++ devel-akpm/drivers/md/raid1.c 2005-08-21 22:35:55.000000000 -0700
@@ -1708,14 +1708,14 @@ void raid1_quiesce(mddev_t *mddev, int s
conf_t *conf = mddev_to_conf(mddev);
switch(state) {
- case 0:
+ case 1:
spin_lock_irq(&conf->resync_lock);
conf->barrier++;
wait_event_lock_irq(conf->wait_idle, !conf->nr_pending,
conf->resync_lock,
raid1_unplug(mddev->queue));
spin_unlock_irq(&conf->resync_lock);
break;
- case 1:
+ case 0:
spin_lock_irq(&conf->resync_lock);
conf->barrier--;
spin_unlock_irq(&conf->resync_lock);
_
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
