From: Zdenek Kabelac <zkabelac@redhat.com>
Date: Fri, 18 Feb 2011 14:26:31 +0000 (+0000)
Subject: Remove fs_unlock after failed suspend
X-Git-Tag: v2_02_91~1100
X-Git-Url: https://sourceware.org/git/?a=commitdiff_plain;h=44376ffe22889652a14791ea8885fe7431bfacaa;p=lvm2.git

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 f73abd935..66ec2c4a8 100644
--- 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 f7da60de3..5c5ad38a4 100644
--- 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;
 	}