From: ccaulfield@sourceware.org <ccaulfield@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW daemons/clvmd/clvmd-corosync.c
Date: 6 Mar 2009 11:29:39 -0000 [thread overview]
Message-ID: <20090306112939.16741.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: ccaulfield at sourceware.org 2009-03-06 11:29:38
Modified files:
. : WHATS_NEW
daemons/clvmd : clvmd-corosync.c
Log message:
Fix unlocks in clvmd-corosync.
The DLM unlock returns EUNLOCK in the lksb on success, not 0
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1062&r2=1.1063
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/daemons/clvmd/clvmd-corosync.c.diff?cvsroot=lvm2&r1=1.6&r2=1.7
--- LVM2/WHATS_NEW 2009/03/05 16:25:35 1.1062
+++ LVM2/WHATS_NEW 2009/03/06 11:29:38 1.1063
@@ -1,6 +1,7 @@
Version 2.02.46 -
================================
Flush memory pool and fix locking in clvmd refresh and backup command.
+ Fix unlocks in clvmd-corosync. Broken in 2.02.45.
Version 2.02.45 - 3rd March 2009
================================
--- LVM2/daemons/clvmd/clvmd-corosync.c 2009/02/25 14:33:01 1.6
+++ LVM2/daemons/clvmd/clvmd-corosync.c 2009/03/06 11:29:38 1.7
@@ -510,7 +510,7 @@
DEBUGLOG("Unlock returned %d\n", err);
return err;
}
- if (lksb.sb_status != 0)
+ if (lksb.sb_status != EUNLOCK)
{
DEBUGLOG("dlm_ls_unlock_wait returns lksb.sb_status: %d\n", lksb.sb_status);
errno = lksb.sb_status;
next reply other threads:[~2009-03-06 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 11:29 ccaulfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-03 13:42 LVM2 ./WHATS_NEW daemons/clvmd/clvmd-corosync.c ccaulfield
2009-04-01 7:51 ccaulfield
2009-02-25 14:33 ccaulfield
2009-02-10 13:22 ccaulfield
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=20090306112939.16741.qmail@sourceware.org \
--to=ccaulfield@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.