From: agk@sourceware.org <agk@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW lib/cache/lvmcache.c
Date: 10 Mar 2011 03:03:04 -0000 [thread overview]
Message-ID: <20110310030304.29678.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk at sourceware.org 2011-03-10 03:03:04
Modified files:
. : WHATS_NEW
lib/cache : lvmcache.c
Log message:
Avoid possible endless loop in _free_vginfo when 4 or more VGs have same name.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1939&r2=1.1940
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/cache/lvmcache.c.diff?cvsroot=lvm2&r1=1.104&r2=1.105
--- LVM2/WHATS_NEW 2011/03/09 12:44:42 1.1939
+++ LVM2/WHATS_NEW 2011/03/10 03:03:03 1.1940
@@ -1,5 +1,6 @@
Version 2.02.85 -
===================================
+ Avoid possible endless loop in _free_vginfo when 4 or more VGs have same name.
Use empty string instead of /dev// for LV path when there's no VG.
Don't allocate unused VG mempool in _pvsegs_sub_single.
Remove uninitialised byte from end of local clvmd messages.
--- LVM2/lib/cache/lvmcache.c 2011/02/21 12:07:03 1.104
+++ LVM2/lib/cache/lvmcache.c 2011/03/10 03:03:04 1.105
@@ -845,7 +845,7 @@
vginfo2->next = vginfo->next;
break;
}
- while ((vginfo2 = primary_vginfo->next));
+ while ((vginfo2 = vginfo2->next));
if (vginfo->vgname)
dm_free(vginfo->vgname);
next reply other threads:[~2011-03-10 3:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 3:03 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-29 21:34 LVM2 ./WHATS_NEW lib/cache/lvmcache.c zkabelac
2010-12-01 10:39 zkabelac
2010-03-31 17:20 mbroz
2009-10-22 17:33 agk
2009-02-17 18:56 agk
2008-11-27 18:13 agk
2008-06-11 11:02 agk
2008-06-09 16:22 agk
2008-05-08 18:28 agk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110310030304.29678.qmail@sourceware.org \
--to=agk@sourceware.org \
--cc=lvm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.