locking: pvmove is locking holding LV

As we do get lock for pvmove LV - it's lockholder ATM.

diff --git a/WHATS_NEW b/WHATS_NEW
index 6ff4ccdf911e91810448899d0c4e80fea70d214c..f29a498d0105c1a22b71588608acb33f6995ab48 100644 (file)
--- a/WHATS_NEW
+++ b/WHATS_NEW
@@ -1,5 +1,6 @@
 Version 2.02.177 -
 ====================================
+  Make a pvmove LV locking holder.
   Do not change critical section counter on resume path without real resume.
   Enhance activation code to automatically suspend pvmove participants.
   Remove unnecessary single read from lvmdiskscan.

diff --git a/lib/metadata/lv.c b/lib/metadata/lv.c
index 4d35efe25c8622fcd5f819f053e726cf7c964c39..630880f515b53b82a564593cb851ed8f40615751 100644 (file)
--- a/lib/metadata/lv.c
+++ b/lib/metadata/lv.c
@@ -1604,6 +1604,9 @@ const struct logical_volume *lv_lock_holder(const struct logical_volume *lv)
        if ((lv_is_raid_image(lv) || lv_is_raid_metadata(lv)) && lv_is_visible(lv))
                return lv;
 
+       if (lv_is_pvmove(lv))
+               return lv;
+
        /* For other types, by default look for the first user */
        dm_list_iterate_items(sl, &lv->segs_using_this_lv) {
                /* FIXME: complete this exception list */