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 lib/metadata/pv_manip.c
Date: Thu, 01 Mar 2012 21:49:00 -0000 [thread overview]
Message-ID: <20120301214933.15593.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: zkabelac@sourceware.org 2012-03-01 21:49:32
Modified files:
. : WHATS_NEW
lib/metadata : pv_manip.c
Log message:
Test alloc fail
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2331&r2=1.2332
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/metadata/pv_manip.c.diff?cvsroot=lvm2&r1=1.31&r2=1.32
--- LVM2/WHATS_NEW 2012/03/01 21:21:54 1.2331
+++ LVM2/WHATS_NEW 2012/03/01 21:49:32 1.2332
@@ -1,5 +1,6 @@
Version 2.02.94 -
====================================
+ Test for alloc fail from _alloc_pv_segment() in _extend_pv().
Check for alloc fail from get_segtype_from_string() in _lvcreate_params().
Add _rimage as reserved suffix to lvm.8 man page.
Improve error logging from mpath filter.
--- LVM2/lib/metadata/pv_manip.c 2011/04/13 18:26:39 1.31
+++ LVM2/lib/metadata/pv_manip.c 2012/03/01 21:49:32 1.32
@@ -442,10 +442,12 @@
return 0;
}
- peg = _alloc_pv_segment(pv->fmt->cmd->mem, pv,
- old_pe_count,
- new_pe_count - old_pe_count,
- NULL, 0);
+ if (!(peg = _alloc_pv_segment(pv->fmt->cmd->mem, pv,
+ old_pe_count,
+ new_pe_count - old_pe_count,
+ NULL, 0)))
+ return_0;
+
dm_list_add(&pv->segments, &peg->list);
pv->pe_count = new_pe_count;
next reply other threads:[~2012-03-01 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 21:49 zkabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-11 15:04 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=20120301214933.15593.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).