public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: prajnoha@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW lib/format_text/format-text.c
Date: Tue, 01 Jun 2010 12:08:00 -0000 [thread overview]
Message-ID: <20100601120851.6570.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: prajnoha@sourceware.org 2010-06-01 12:08:51
Modified files:
. : WHATS_NEW
lib/format_text: format-text.c
Log message:
Fix incorrect memory pool deallocation while using vg_read for files.
We create a separate pool "lvm2 vg_read" for vg_read and we don't use
cmd->mem anymore.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1600&r2=1.1601
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/format_text/format-text.c.diff?cvsroot=lvm2&r1=1.121&r2=1.122
--- LVM2/WHATS_NEW 2010/05/28 03:50:15 1.1600
+++ LVM2/WHATS_NEW 2010/06/01 12:08:50 1.1601
@@ -1,5 +1,6 @@
Version 2.02.67 -
===============================
+ Fix incorrect memory pool deallocation while using vg_read for files.
Add --type parameter description to the lvcreate man page.
Replace strncmp kernel version number checks with proper ones.
Avoid selecting names under /dev/block if there is an alternative.
--- LVM2/lib/format_text/format-text.c 2010/04/14 13:09:16 1.121
+++ LVM2/lib/format_text/format-text.c 2010/06/01 12:08:50 1.122
@@ -814,7 +814,7 @@
* check that it contains the correct volume group.
*/
if (vgname && strcmp(vgname, vg->name)) {
- dm_pool_free(fid->fmt->cmd->mem, vg);
+ dm_pool_destroy(vg->vgmem);
log_error("'%s' does not contain volume group '%s'.",
read_path, vgname);
return NULL;
next reply other threads:[~2010-06-01 12:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 12:08 prajnoha [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-13 11:09 zkabelac
2011-08-29 13:37 prajnoha
2011-02-03 1:41 zkabelac
2010-10-26 9:13 zkabelac
2010-09-30 14:12 prajnoha
2009-07-30 21:15 snitzer
2009-07-30 18:40 snitzer
2009-07-30 17:42 snitzer
2009-07-30 17:19 snitzer
2009-07-30 17:18 snitzer
2009-03-23 21:13 taka
2009-03-03 16:35 mbroz
2008-10-17 0:55 agk
2008-09-30 20:37 agk
2008-08-16 9:46 mbroz
2008-07-31 10:50 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=20100601120851.6570.qmail@sourceware.org \
--to=prajnoha@sourceware.org \
--cc=lvm-devel@redhat.com \
--cc=lvm2-cvs@sourceware.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).