From: wysochanski@sourceware.org <wysochanski@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW tools/vgsplit.c
Date: 8 Apr 2008 21:38:09 -0000 [thread overview]
Message-ID: <20080408213809.13010.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: wysochanski at sourceware.org 2008-04-08 21:38:09
Modified files:
. : WHATS_NEW
tools : vgsplit.c
Log message:
Fix vgsplit error paths to release vg_to lock.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.832&r2=1.833
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/vgsplit.c.diff?cvsroot=lvm2&r1=1.54&r2=1.55
--- LVM2/WHATS_NEW 2008/04/08 14:22:12 1.832
+++ LVM2/WHATS_NEW 2008/04/08 21:38:08 1.833
@@ -1,5 +1,6 @@
Version 2.02.34 -
===================================
+ Fix vgsplit error paths to release vg_to lock.
Indicate whether or not VG is clustered in vgcreate log message.
Mention default --clustered setting in vgcreate man page.
Add config file overrides to clvmd when it reads the active LVs list.
--- LVM2/tools/vgsplit.c 2008/04/02 19:30:12 1.54
+++ LVM2/tools/vgsplit.c 2008/04/08 21:38:09 1.55
@@ -288,11 +288,13 @@
if (fill_vg_create_params(cmd, vg_name_to, &vp_new, &vp_def)) {
unlock_vg(cmd, vg_name_from);
+ unlock_vg(cmd, vg_name_to);
return EINVALID_CMD_LINE;
}
if (validate_vg_create_params(cmd, &vp_new)) {
unlock_vg(cmd, vg_name_from);
+ unlock_vg(cmd, vg_name_to);
return EINVALID_CMD_LINE;
}
next reply other threads:[~2008-04-08 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 21:38 wysochanski [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-08 21:47 LVM2 ./WHATS_NEW tools/vgsplit.c wysochanski
2008-04-02 19:30 wysochanski
2008-04-02 13:08 wysochanski
2007-06-28 17:59 mbroz
2007-05-15 13:01 mbroz
2006-10-13 13:22 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=20080408213809.13010.qmail@sourceware.org \
--to=wysochanski@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.