[dm-devel] [PATCH 3/4] [block-manager] remove spurious decrement of write_lock_pending in the case of a recycled block.
Joe Thornber
ejt at redhat.com
Tue Aug 2 14:36:47 UTC 2011
---
drivers/md/persistent-data/dm-block-manager.c | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/drivers/md/persistent-data/dm-block-manager.c b/drivers/md/persistent-data/dm-block-manager.c
index b68be88..d27ab6e 100644
--- a/drivers/md/persistent-data/dm-block-manager.c
+++ b/drivers/md/persistent-data/dm-block-manager.c
@@ -756,9 +756,15 @@ retry:
b->write_lock_pending++;
__wait_unlocked(b, &flags);
- b->write_lock_pending--;
if (b->where != block)
+ /*
+ * Recycled blocks have their
+ * write_lock_pending count reset
+ * to zero, so no need to undo the
+ * above increment.
+ */
goto retry;
+ b->write_lock_pending--;
}
break;
}
--
1.7.4.1
More information about the dm-devel
mailing list