summaryrefslogtreecommitdiff
path: root/WHATS_NEW
diff options
context:
space:
mode:
authorZdenek Kabelac <zkabelac@redhat.com>2013-06-18 21:50:29 +0200
committerZdenek Kabelac <zkabelac@redhat.com>2013-06-18 22:11:21 +0200
commit25629688643958e12859af0d53e818b8b111b4a9 (patch)
tree516139e7a7897ef3b5dac0bd4b4febc48988a32e /WHATS_NEW
parent1acad23d68b6b82a297fb4106f016ae7a15fcf1a (diff)
downloadlvm2-25629688643958e12859af0d53e818b8b111b4a9.tar.gz
vgcfgrestore: fix crash on restore of wrong vgname
When vgname has not existed in metadata, it has crashed on double free in format_instance destroy() - since VG was created, used FID and was released - which also released FID, so further use was accessing bad memory. Fix it for this code path before release_vg() so FID will exists when _vg_read_file_name() returns NULL.
Diffstat (limited to 'WHATS_NEW')
-rw-r--r--WHATS_NEW1
1 files changed, 1 insertions, 0 deletions
diff --git a/WHATS_NEW b/WHATS_NEW
index 97e3ebfb0..1eb440fb3 100644
--- a/WHATS_NEW
+++ b/WHATS_NEW
@@ -1,5 +1,6 @@
Version 2.02.99 -
===================================
+ Fix vgcfgrestore crash when specified incorrect vg name.
Refine lvm.conf and man page documentation for autoactivation feature.
Add support for thin volumes in vgsplit.
Also filter partitions on mpath components if multipath_component_detection=1.