From: zkabelac@sourceware.org <zkabelac@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW lib/format_text/import_vsn1.c
Date: 25 Jan 2012 21:43:51 -0000 [thread overview]
Message-ID: <20120125214351.28803.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: zkabelac at sourceware.org 2012-01-25 21:43:51
Modified files:
. : WHATS_NEW
lib/format_text: import_vsn1.c
Log message:
Check for correctness of uint64 value if exists
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2240&r2=1.2241
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/format_text/import_vsn1.c.diff?cvsroot=lvm2&r1=1.98&r2=1.99
--- LVM2/WHATS_NEW 2012/01/25 13:10:26 1.2240
+++ LVM2/WHATS_NEW 2012/01/25 21:43:51 1.2241
@@ -1,5 +1,6 @@
Version 2.02.89 -
==================================
+ Check for correctness of uint64 dev_size value.
Rename origin_only parameter to more generic flag use_layer for lv_info().
Thin pools have segment fields thin_count, zero, transaction_id.
Each new created LV volume has creation lv_time and lv_host.
--- LVM2/lib/format_text/import_vsn1.c 2012/01/19 15:31:45 1.98
+++ LVM2/lib/format_text/import_vsn1.c 2012/01/25 21:43:51 1.99
@@ -216,7 +216,11 @@
pv->status |= MISSING_PV;
/* Late addition */
- _read_uint64(pvn, "dev_size", &pv->size);
+ if (dm_config_has_node(pvn, "dev_size") &&
+ !_read_uint64(pvn, "dev_size", &pv->size)) {
+ log_error("Couldn't read dev size for physical volume.");
+ return 0;
+ }
if (!_read_uint64(pvn, "pe_start", &pv->pe_start)) {
log_error("Couldn't read extent size for physical volume.");
next reply other threads:[~2012-01-25 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 21:43 zkabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-21 12:49 LVM2 ./WHATS_NEW lib/format_text/import_vsn1.c zkabelac
2011-10-23 16:05 zkabelac
2010-03-31 17:20 mbroz
2009-07-09 11:29 mbroz
2009-07-09 11:28 mbroz
2009-03-09 15:42 wysochanski
2007-11-04 15:43 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=20120125214351.28803.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.