From: Chrissie Caulfield <ccaulfie@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] clvmd-corosync should check lksb.sb_status instead of return code ?
Date: Wed, 25 Feb 2009 13:52:56 +0000 [thread overview]
Message-ID: <49A54D38.9030309@redhat.com> (raw)
In-Reply-To: <1cafab770902250534m38e712cepc2f0c3e80ad93257@mail.gmail.com>
Xinwei Hu wrote:
> Hi Chrissie,
>
> You are right. It should be returned in errno. Also, it seems errno
> should positive as lksb.sb_status too.
>
> I modified the patch a little bit further.
>
> Any comments ?
Hi
You're right ... this kernel-itis is catching! lksb status are indeed
positive and correct for returning as errno.
I'll commit this patch
Thank you.
Chrissie
> 2009/2/25 Chrissie Caulfield <ccaulfie@redhat.com>:
>> Xinwei Hu wrote:
>>> Hi all,
>>>
>>> In clvmd-corosync, lock_resource calls dlm_ls_lock_wait with flags
>>> set to LKF_NOQUEUE.
>>> When LKF_NOQUEUE is set, the return code of dlm_ls_lock_wait is
>>> always 0, while the actual errno is in lksb.sb_status.
>>>
>>> This causes problem when using vgchange -aey or something like.
>>>
>>> I attached a patch to try to fix this issue.
>>>
>>> Please help to review. Thanks.
>> Hi
>>
>> You are correct, the functions do need to check the LKSB. Your patch
>> isn't quite right I don't think though - the lksb status should be
>> returned in errno as shown below:
>>
>> --
>>
>> Chrissie
next prev parent reply other threads:[~2009-02-25 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 10:35 [linux-lvm] clvmd-corosync should check lksb.sb_status instead of return code ? Xinwei Hu
2009-02-25 13:30 ` Chrissie Caulfield
2009-02-25 13:34 ` Xinwei Hu
2009-02-25 13:52 ` Chrissie Caulfield [this message]
2009-02-25 14:07 ` Xinwei Hu
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=49A54D38.9030309@redhat.com \
--to=ccaulfie@redhat.com \
--cc=linux-lvm@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.