From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 4/4] ocfs2/dlm: return EINVAL when the lockres on migration target is in DROPPING_REF state
Date: Wed, 27 Jan 2016 09:39:07 +0800 [thread overview]
Message-ID: <56A81FBB.9080002@huawei.com> (raw)
In-Reply-To: <56A73FE9.3010007@huawei.com>
On 2016/1/26 17:44, xuejiufei wrote:
> If master migrate this lock resource to node when it happened to purge
> it, a new lock resource will be created and inserted into hash list. If
> then master goes down, the lock resource being purged is recovered, so
> there exist two lock resource with different owner. So return error to
> master if the lock resource is in DROPPING state, master will retry to
> migrate this lock resource.
>
> Signed-off-by: xuejiufei <xuejiufei@huawei.com>
Reviewed-by: Joseph Qi <joseph.qi@huawei.com>
> ---
> fs/ocfs2/dlm/dlmrecovery.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/fs/ocfs2/dlm/dlmrecovery.c b/fs/ocfs2/dlm/dlmrecovery.c
> index c19059a..4c7b548 100644
> --- a/fs/ocfs2/dlm/dlmrecovery.c
> +++ b/fs/ocfs2/dlm/dlmrecovery.c
> @@ -1403,12 +1403,24 @@ int dlm_mig_lockres_handler(struct o2net_msg *msg, u32 len, void *data,
> * and RECOVERY flag changed when it completes. */
> hash = dlm_lockid_hash(mres->lockname, mres->lockname_len);
> spin_lock(&dlm->spinlock);
> - res = __dlm_lookup_lockres(dlm, mres->lockname, mres->lockname_len,
> + res = __dlm_lookup_lockres_full(dlm, mres->lockname, mres->lockname_len,
> hash);
> if (res) {
> /* this will get a ref on res */
> /* mark it as recovering/migrating and hash it */
> spin_lock(&res->spinlock);
> + if (res->state & DLM_LOCK_RES_DROPPING_REF) {
> + mlog(0, "%s: node is attempting to migrate "
> + "lockres %.*s, but marked as dropping "
> + " ref!\n", dlm->name,
> + mres->lockname_len, mres->lockname);
> + ret = -EINVAL;
> + spin_unlock(&res->spinlock);
> + spin_unlock(&dlm->spinlock);
> + dlm_lockres_put(res);
> + goto leave;
> + }
> +
> if (mres->flags & DLM_MRES_RECOVERY) {
> res->state |= DLM_LOCK_RES_RECOVERING;
> } else {
>
prev parent reply other threads:[~2016-01-27 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 9:44 [Ocfs2-devel] [PATCH 4/4] ocfs2/dlm: return EINVAL when the lockres on migration target is in DROPPING_REF state xuejiufei
2016-01-27 1:39 ` 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=56A81FBB.9080002@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 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 NNTP newsgroup(s).