From 44376ffe22889652a14791ea8885fe7431bfacaa Mon Sep 17 00:00:00 2001 From: Zdenek Kabelac Date: Fri, 18 Feb 2011 14:26:31 +0000 Subject: [PATCH] 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(). --- WHATS_NEW | 1 + lib/activate/activate.c | 1 - 2 files changed, 1 insertion(+), 1 deletion(-) 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; }