From: zkabelac@sourceware.org <zkabelac@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 lib/commands/toolcontext.c ./WHATS_NEW
Date: 29 Nov 2010 10:58:33 -0000 [thread overview]
Message-ID: <20101129105833.5420.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: zkabelac at sourceware.org 2010-11-29 10:58:33
Modified files:
lib/commands : toolcontext.c
. : WHATS_NEW
Log message:
Fix check for empty system_dir
Fixing check for zero length system_dir string.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/commands/toolcontext.c.diff?cvsroot=lvm2&r1=1.109&r2=1.110
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1810&r2=1.1811
--- LVM2/lib/commands/toolcontext.c 2010/11/24 09:34:35 1.109
+++ LVM2/lib/commands/toolcontext.c 2010/11/29 10:58:32 1.110
@@ -1036,7 +1036,7 @@
char default_dir[PATH_MAX];
const char *dir;
- if (!cmd->system_dir) {
+ if (!cmd->system_dir[0]) {
log_warn("WARNING: Metadata changes will NOT be backed up");
backup_init(cmd, "", 0);
archive_init(cmd, "", 0, 0, 0);
--- LVM2/WHATS_NEW 2010/11/25 17:16:41 1.1810
+++ LVM2/WHATS_NEW 2010/11/29 10:58:33 1.1811
@@ -1,5 +1,6 @@
Version 2.02.78 -
====================================
+ Fix test for empty system_dir string in _init_backup().
Certain lvconvert invocations are now required to be done in two steps.
Fix missing context desctruction in err path of lvm1 fallback in lvm2_main().
Fix memory leak in error path of parse_loop_device_name() from dmsetup.
next reply other threads:[~2010-11-29 10:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 10:58 zkabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-01 21:47 LVM2 lib/commands/toolcontext.c ./WHATS_NEW wysochanski
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=20101129105833.5420.qmail@sourceware.org \
--to=zkabelac@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.