public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: zkabelac@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW tools/lvresize.c
Date: Wed, 08 Feb 2012 10:56:00 -0000 [thread overview]
Message-ID: <20120208105621.24354.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: zkabelac@sourceware.org 2012-02-08 10:56:18
Modified files:
. : WHATS_NEW
tools : lvresize.c
Log message:
Set status for error path
Do not leave status unitialized, since in some cases, it's tested,
when the function returns error.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2261&r2=1.2262
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/lvresize.c.diff?cvsroot=lvm2&r1=1.148&r2=1.149
--- LVM2/WHATS_NEW 2012/02/08 10:52:45 1.2261
+++ LVM2/WHATS_NEW 2012/02/08 10:56:17 1.2262
@@ -1,5 +1,6 @@
Version 2.02.91 -
===================================
+ Set status in _fsadm_cmd() for error path.
Add missing deps for lvm2api for rebuild when lvm-internal is changed.
Fix resource leaks for failing allocation of formats (lvm1/2,pool).
Release allocated resources in error path for composite_filter_create().
--- LVM2/tools/lvresize.c 2012/01/19 15:25:39 1.148
+++ LVM2/tools/lvresize.c 2012/02/08 10:56:18 1.149
@@ -159,6 +159,9 @@
argv[i++] = (fcmd == FSADM_CMD_RESIZE) ? "resize" : "check";
+ if (status)
+ *status = -1;
+
if (dm_snprintf(lv_path, PATH_MAX, "%s%s/%s", cmd->dev_dir, lp->vg_name,
lp->lv_name) < 0) {
log_error("Couldn't create LV path for %s", lp->lv_name);
next reply other threads:[~2012-02-08 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 10:56 zkabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-11 12:40 zkabelac
2012-04-11 12:36 zkabelac
2012-01-09 12:31 zkabelac
2011-12-01 0:13 jbrassow
2010-03-20 3:44 snitzer
2009-01-15 14:44 wysochanski
2008-09-18 18:52 agk
2008-04-01 22:15 wysochanski
2004-11-18 19:49 agk
2004-05-24 15:58 agk
2004-05-11 18:47 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=20120208105621.24354.qmail@sourceware.org \
--to=zkabelac@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).