Remove fs_unlock after failed suspend

Explicit fs_unlock() after failed suspend is not need -
as it will happen automatically with nearest lv_info()
or vg_unlock().

diff --git a/WHATS_NEW b/WHATS_NEW
index f73abd935d91ad6f8ba69dab1b7767e5f4976390..66ec2c4a88a67a8f23252626a9401a12c1a684f4 100644 (file)
--- a/WHATS_NEW
+++ b/WHATS_NEW
@@ -1,5 +1,6 @@
 Version 2.02.85 - 
 ===================================
+  Remove fs_unlock() from lv_suspend error path.
   Change memory locking semantic and use critical sections.
   Add configurable pv_min_size to select block devices by its size.
   Add function to read 64bit ints from config find_config_tree_int64.

diff --git a/lib/activate/activate.c b/lib/activate/activate.c
index f7da60de3500c3890cd1bae2b3d83b8930227211..5c5ad38a4eb48c3a91f3c61f25b8e03e80a715bd 100644 (file)
--- a/lib/activate/activate.c
+++ b/lib/activate/activate.c
@@ -1126,7 +1126,6 @@ static int _lv_suspend(struct cmd_context *cmd, const char *lvid_s,
 
        if (!_lv_suspend_lv(lv, origin_only, lockfs, flush_required)) {
                critical_section_dec(cmd);
-               fs_unlock();
                goto out;
        }