[lvm-devel] [PATCH 04/12] Unlock memory for vg_write
Zdenek Kabelac
zkabelac at redhat.com
Wed Nov 16 13:22:51 UTC 2011
For write we do not need to hold memory locked.
We should never write metadata in locked state.
This relaxes meny conditions and avoid problems when allocating
a lot of memory for writting metadata buffers.
(In case of huge MDA size this would lead to mismatch between
locked and unlocked memory size).
Signed-off-by: Zdenek Kabelac <zkabelac at redhat.com>
---
lib/metadata/metadata.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/lib/metadata/metadata.c b/lib/metadata/metadata.c
index 4037c0e..f9742e7 100644
--- a/lib/metadata/metadata.c
+++ b/lib/metadata/metadata.c
@@ -2573,6 +2573,8 @@ int vg_write(struct volume_group *vg)
return 0;
}
+ /* Unlock memory if possible */
+ memlock_unlock(vg->cmd);
vg->seqno++;
dm_list_iterate_items(pv_to_create, &vg->pvs_to_create) {
--
1.7.7.3
More information about the lvm-devel
mailing list