From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH V2] ocfs2/dlm: clear migration_pending when migration target goes down
Date: Thu, 24 Dec 2015 15:48:26 +0800 [thread overview]
Message-ID: <567BA34A.4080104@huawei.com> (raw)
In-Reply-To: <567B9CBB.7000904@huawei.com>
On 2015/12/24 15:20, xuejiufei wrote:
> We have found a BUG on res->migration_pending when migrating
> lock resources. The situation is as follows.
>
> dlm_mark_lockres_migration
> res->migration_pending = 1;
> __dlm_lockres_reserve_ast
> dlm_lockres_release_ast returns with res->migration_pending remains
> because other threads reserve asts
> wait dlm_migration_can_proceed returns 1
> >>>>>>> o2hb found that target goes down and remove target
> from domain_map
> dlm_migration_can_proceed returns 1
> dlm_mark_lockres_migrating returns -ESHOTDOWN with
> res->migration_pending still remains.
>
> When reentering dlm_mark_lockres_migrating(), it will trigger
> the BUG_ON with res->migration_pending. So clear migration_pending
> when target is down.
>
> Signed-off-by: Jiufei Xue <xuejiufei@huawei.com>
Reviewed-by: Joseph Qi <joseph.qi@huawei.com>
> ---
> fs/ocfs2/dlm/dlmmaster.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/ocfs2/dlm/dlmmaster.c b/fs/ocfs2/dlm/dlmmaster.c
> index c43da7f..936e11b 100644
> --- a/fs/ocfs2/dlm/dlmmaster.c
> +++ b/fs/ocfs2/dlm/dlmmaster.c
> @@ -2843,6 +2843,8 @@ again:
> res->state &= ~DLM_LOCK_RES_BLOCK_DIRTY;
> if (!ret)
> BUG_ON(!(res->state & DLM_LOCK_RES_MIGRATING));
> + else
> + res->migration_pending = 0;
> spin_unlock(&res->spinlock);
>
> /*
>
prev parent reply other threads:[~2015-12-24 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 7:20 [Ocfs2-devel] [PATCH V2] ocfs2/dlm: clear migration_pending when migration target goes down xuejiufei
2015-12-24 7:48 ` Joseph Qi [this message]
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=567BA34A.4080104@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.