All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH v2] ocfs2/dlm: fix race between convert and recovery
Date: Tue, 22 Sep 2015 20:23:59 +0800	[thread overview]
Message-ID: <5601485F.4030506@huawei.com> (raw)
In-Reply-To: <5600A6FD.90901@oracle.com>

Hi Junxiao,

On 2015/9/22 8:55, Junxiao Bi wrote:
> On 09/21/2015 05:23 PM, Joseph Qi wrote:
>> Hi Junxiao,
>> This solution may have problem in the following scenario:
>> Consider dlm_send_remote_convert_request has taken too much time, and
>> dlm_move_lockres_to_recovery_list runs first and new master will see
>> this node is currently in convert list after recovery.
>> Then dlm_send_remote_convert_request returns other than DLM_NORMAL and
>> it will revert it to grant list, then retry convert. This will makes
>> this node and master inconsistent.
>> I will try to find another solution to resolve the race issue.
> 
> If master is down, no need retry convert. May check the return value of
> dlm_send_remote_convert_request(), if DLM_RECOVERING, don't retry,
> otherwise retry?

I want to keep the original logic. And for fixing the race case I
described, how about the following idea?

Check the status DLM_NORMAL. If res->state is currently
DLM_LOCK_RES_RECOVERING (set in dlm_move_lockres_to_recovery_list, means
still in recovery) or res master changed (means new master has finished
the recovery), reset the status to DLM_RECOVERING, just like the check
at the beginning of dlmconvert_remote. Then it is now in grant list and
outer will retry.

> 
> Thanks,
> Junxiao.
> 
>>
>> On 2015/9/20 15:20, Junxiao Bi wrote:
>>> Reviewed-by: Junxiao Bi <junxiao.bi@oracle.com>
>>>
>>>>> ? 2015?9?18????7:25?Joseph Qi <joseph.qi@huawei.com> ???
>>>>>
>>>>> There is a race window between dlmconvert_remote and
>>>>> dlm_move_lockres_to_recovery_list, which will cause a lock with
>>>>> OCFS2_LOCK_BUSY in grant list, thus system hangs.
>>>>>
>>>>> dlmconvert_remote
>>>>> {	
>>>>>        spin_lock(&res->spinlock);
>>>>>        list_move_tail(&lock->list, &res->converting);
>>>>>        lock->convert_pending = 1;
>>>>>        spin_unlock(&res->spinlock);
>>>>>
>>>>>        status = dlm_send_remote_convert_request();
>>>>>>>>>>>>>>>>> race window, master has queued ast and return DLM_NORMAL,
>>>>>               and then down before sending ast.
>>>>>               this node detects master down and calls
>>>>>               dlm_move_lockres_to_recovery_list, which will revert the
>>>>>               lock to grant list.
>>>>>               Then OCFS2_LOCK_BUSY won't be cleared as new master won't
>>>>>               send ast any more because it thinks already be authorized.
>>>>>
>>>>>        spin_lock(&res->spinlock);
>>>>>        lock->convert_pending = 0;
>>>>>        if (status != DLM_NORMAL)
>>>>>                dlm_revert_pending_convert(res, lock);
>>>>>        spin_unlock(&res->spinlock);
>>>>> }
>>>>>
>>>>> In this case, just leave it in convert list and new master will take care
>>>>> of it after recovery.  And if convert request returns other than
>>>>> DLM_NORMAL, convert thread will do the revert itself. So remove the
>>>>> revert logic in dlm_move_lockres_to_recovery_list.
>>>>>
>>>>> changelog since v1:
>>>>> Clean up convert_pending since it is now useless.
>>
>>
> 
> 
> .
> 

  reply	other threads:[~2015-09-22 12:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18 11:25 [Ocfs2-devel] [PATCH v2] ocfs2/dlm: fix race between convert and recovery Joseph Qi
2015-09-20  7:20 ` Junxiao Bi
2015-09-21  9:23   ` Joseph Qi
2015-09-22  0:55     ` Junxiao Bi
2015-09-22 12:23       ` Joseph Qi [this message]
2015-09-23  1:25         ` Junxiao Bi
2015-09-23  1:47           ` Joseph Qi
2015-09-23  1:59             ` Junxiao Bi
2015-09-23  7:48               ` Joseph Qi
2015-09-23  8:42                 ` Junxiao Bi

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=5601485F.4030506@huawei.com \
    --to=joseph.qi@huawei.com \
    --cc=ocfs2-devel@oss.oracle.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.