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/locking/locking.h
Date: Fri, 21 May 2010 14:29:00 -0000 [thread overview]
Message-ID: <20100521142951.27953.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: zkabelac@sourceware.org 2010-05-21 14:29:49
Modified files:
. : WHATS_NEW
lib/locking : locking.h
Log message:
Replicator: lock_lv_vol() finds missing VGs
Find and check for all needed VGs before calling lock_vol().
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1587&r2=1.1588
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/locking/locking.h.diff?cvsroot=lvm2&r1=1.55&r2=1.56
--- LVM2/WHATS_NEW 2010/05/21 14:15:39 1.1587
+++ LVM2/WHATS_NEW 2010/05/21 14:29:49 1.1588
@@ -1,5 +1,6 @@
Version 2.02.67 -
===============================
+ Check for missing VGs before taking lock_lv_vol (for Replicator).
Update process_each_lv_in_vg() to use cmd_vg structure.
Update _process_one_vg() to work with cmd_vg structure.
Add functions for read and release VGs list.
--- LVM2/lib/locking/locking.h 2010/05/19 01:49:08 1.55
+++ LVM2/lib/locking/locking.h 2010/05/21 14:29:49 1.56
@@ -130,7 +130,9 @@
(vg_is_clustered((lv)->vg) ? LCK_CLUSTER_VG : 0)
#define lock_lv_vol(cmd, lv, flags) \
- lock_vol(cmd, (lv)->lvid.s, flags | LCK_LV_CLUSTERED(lv))
+ (find_replicator_vgs((lv)) ? \
+ lock_vol(cmd, (lv)->lvid.s, flags | LCK_LV_CLUSTERED(lv)) : \
+ 0)
#define unlock_vg(cmd, vol) lock_vol(cmd, vol, LCK_VG_UNLOCK)
#define unlock_and_release_vg(cmd, vg, vol) \
next reply other threads:[~2010-05-21 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 14:29 zkabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-15 13:24 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=20100521142951.27953.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).