mirror of
git://sourceware.org/git/lvm2.git
synced 2024-12-21 13:34:40 +03:00
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().
This commit is contained in:
parent
b1bcff7424
commit
44376ffe22
@ -1,5 +1,6 @@
|
|||||||
Version 2.02.85 -
|
Version 2.02.85 -
|
||||||
===================================
|
===================================
|
||||||
|
Remove fs_unlock() from lv_suspend error path.
|
||||||
Change memory locking semantic and use critical sections.
|
Change memory locking semantic and use critical sections.
|
||||||
Add configurable pv_min_size to select block devices by its size.
|
Add configurable pv_min_size to select block devices by its size.
|
||||||
Add function to read 64bit ints from config find_config_tree_int64.
|
Add function to read 64bit ints from config find_config_tree_int64.
|
||||||
|
@ -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)) {
|
if (!_lv_suspend_lv(lv, origin_only, lockfs, flush_required)) {
|
||||||
critical_section_dec(cmd);
|
critical_section_dec(cmd);
|
||||||
fs_unlock();
|
|
||||||
goto out;
|
goto out;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user