[lvm-devel] [PATCH 15/24] Remove fs_unlock after failed suspend
Zdenek Kabelac
zkabelac at redhat.com
Sun Jan 30 12:57:38 UTC 2011
Explicit fs_unlock() after failed suspend is not need -
as it will happen automatically with nearest lv_info()
or vg_unlock().
Signed-off-by: Zdenek Kabelac <zkabelac at redhat.com>
---
lib/activate/activate.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/lib/activate/activate.c b/lib/activate/activate.c
index 4e862f5..b320021 100644
--- a/lib/activate/activate.c
+++ b/lib/activate/activate.c
@@ -1057,7 +1057,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;
}
--
1.7.3.5
More information about the lvm-devel
mailing list