public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: mbroz@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW tools/pvchange.c
Date: Thu, 23 Dec 2010 14:23:00 -0000 [thread overview]
Message-ID: <20101223142331.23379.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: mbroz@sourceware.org 2010-12-23 14:23:30
Modified files:
. : WHATS_NEW
tools : pvchange.c
Log message:
Fix wrongly paired unlocking of global lock in pvchange. (2.02.66)
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1855&r2=1.1856
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/pvchange.c.diff?cvsroot=lvm2&r1=1.86&r2=1.87
--- LVM2/WHATS_NEW 2010/12/22 15:36:41 1.1855
+++ LVM2/WHATS_NEW 2010/12/23 14:23:30 1.1856
@@ -1,5 +1,6 @@
Version 2.02.80 -
====================================
+ Fix wrongly paired unlocking of global lock in pvchange. (2.02.66)
Add backtraces for backup and backup_remove fail paths.
Detect errors from dm_task_set calls in _get_device_info (dmeventd).
Add backtraces for archive and backup_locally in check_current_backup().
--- LVM2/tools/pvchange.c 2010/12/08 20:50:51 1.86
+++ LVM2/tools/pvchange.c 2010/12/23 14:23:30 1.87
@@ -288,9 +288,9 @@
unlock_and_free_vg(cmd, vg, sll->str);
}
}
+ unlock_vg(cmd, VG_GLOBAL);
}
- unlock_vg(cmd, VG_GLOBAL);
log_print("%d physical volume%s changed / %d physical volume%s "
"not changed",
done, done == 1 ? "" : "s",
next reply other threads:[~2010-12-23 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 14:23 mbroz [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-31 12:28 agk
2008-07-16 10:46 agk
2005-05-24 17:38 agk
2004-12-21 16:12 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=20101223142331.23379.qmail@sourceware.org \
--to=mbroz@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).