public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: agk@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW lib/locking/locking.c
Date: Sun, 22 Feb 2009 16:13:00 -0000 [thread overview]
Message-ID: <20090222161358.22749.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk@sourceware.org 2009-02-22 16:13:57
Modified files:
. : WHATS_NEW
lib/locking : locking.c
Log message:
Fix interrupt unblocking after vgcreate, for example: drop_cached_metadata()
previously left _vg_lock_count incremented.
Other locks are always held during drop_cached_metadata() so there's no
need to increment+decrement it.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1046&r2=1.1047
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/locking/locking.c.diff?cvsroot=lvm2&r1=1.55&r2=1.56
--- LVM2/WHATS_NEW 2009/02/20 23:19:28 1.1046
+++ LVM2/WHATS_NEW 2009/02/22 16:13:57 1.1047
@@ -1,5 +1,6 @@
Version 2.02.45 -
===================================
+ Exclude LCK_CACHE locks from _vg_lock_count, fixing interrupt unblocking.
Provide da and mda locations in debug message when writing text format label.
Mention the restriction on file descriptors at invocation on the lvm man page.
Index cached vgmetadata by vgid not vgname to cope with duplicate vgnames.
--- LVM2/lib/locking/locking.c 2009/02/03 16:23:19 1.55
+++ LVM2/lib/locking/locking.c 2009/02/22 16:13:57 1.56
@@ -191,7 +191,8 @@
static void _update_vg_lock_count(uint32_t flags)
{
- if ((flags & LCK_SCOPE_MASK) != LCK_VG)
+ if ((flags & LCK_SCOPE_MASK) != LCK_VG ||
+ (flags & LCK_CACHE))
return;
if ((flags & LCK_TYPE_MASK) == LCK_UNLOCK)
next reply other threads:[~2009-02-22 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 16:13 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-27 15:53 mbroz
2011-08-10 16:07 mbroz
2011-01-13 14:56 zkabelac
2010-03-31 17:23 mbroz
2010-01-13 17:40 mbroz
2009-11-23 10:55 mbroz
2009-07-14 11:01 agk
2008-05-08 18:35 agk
2006-10-14 16:37 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=20090222161358.22749.qmail@sourceware.org \
--to=agk@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).