public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: mornfall@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW lib/locking/no_locking.c
Date: Sun, 02 Aug 2009 21:03:00 -0000 [thread overview]
Message-ID: <20090802210309.20342.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: mornfall@sourceware.org 2009-08-02 21:03:09
Modified files:
. : WHATS_NEW
lib/locking : no_locking.c
Log message:
Allow LV suspend while --ignorelockingfailure is in force.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1226&r2=1.1227
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/locking/no_locking.c.diff?cvsroot=lvm2&r1=1.17&r2=1.18
--- LVM2/WHATS_NEW 2009/08/02 21:01:51 1.1226
+++ LVM2/WHATS_NEW 2009/08/02 21:03:09 1.1227
@@ -1,5 +1,6 @@
Version 2.02.51 -
================================
+ Allow LV suspend while --ignorelockingfailure is in force.
Update synopsis in lvconvert manpage to mention --repair.
Set cookies in activation code and wait for udev to complete processing.
Added configure --enable-udev_rules --enable-udev_sync.
--- LVM2/lib/locking/no_locking.c 2009/07/15 06:11:25 1.17
+++ LVM2/lib/locking/no_locking.c 2009/08/02 21:03:09 1.18
@@ -70,7 +70,8 @@
const char *resource,
uint32_t flags)
{
- if ((flags & LCK_TYPE_MASK) == LCK_WRITE) {
+ if ((flags & LCK_TYPE_MASK) == LCK_WRITE &&
+ (flags & LCK_SCOPE_MASK) == LCK_VG) {
log_error("Write locks are prohibited with --ignorelockingfailure.");
return 0;
}
next reply other threads:[~2009-08-02 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 21:03 mornfall [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-13 14:59 pcaulfield
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=20090802210309.20342.qmail@sourceware.org \
--to=mornfall@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).