From: Xiaowei.hu <xiaowei.hu@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Race condition between OCFS2 downconvert thread and ocfs2 cluster lock.
Date: Wed, 22 Feb 2012 08:36:14 +0800 [thread overview]
Message-ID: <4F44387E.7040502@oracle.com> (raw)
In-Reply-To: <4F43D90B.8040802@oracle.com>
Hi Sunil,
I mean it execute in this way:
nodeA ocfs2_dlm_lock() and released the res spin lock,here A doesn't
hold spin locks,
then it start to execute the proxy ast handler , process bast request
from nodeB,
then dlmthread flushed the bast, after this node A start to queue its
ast in ocfs2_dlm_lock() function.
Thanks,
Xiaowei
On 02/22/2012 01:48 AM, Sunil Mushran wrote:
> > bast queued and flushed,before the ast was queued
>
> Unlikely with o2dlm. dlmthread always sends ASTs before BASTs.
>
> Can you recreate the entire lockres? A full dump may yield more
> information.
>
> Sunil
>
> On 02/20/2012 10:12 PM, xiaowei.hu at oracle.com wrote:
>> I am trying to fix bug13611997,CT's machine run into BUG in ocfs2dc
>> thread, BUG_ON(lockres->l_action != OCFS2_AST_CONVERT&&
>> lockres->l_action != OCFS2_AST_DOWNCONVERT); I analysized the vmcore
>> , the lockres->l_action = OCFS2_AST_ATTACH and l_flags=326(which
>> means
>> OCFS2_LOCK_BUSY|OCFS2_LOCK_BLOCKED|OCFS2_LOCK_INITIALIZED|OCFS2_LOCK_QUEUED),
>> after compared with the code , this status could be only possible
>> during ocfs2_cluster_lock,here is the race situation:
>>
>> NodeA NodeB
>> ocfs2_cluster_lock on a new lockres M
>> spin_lock_irqsave(&lockres->l_lock, flags);
>> gen = lockres_set_pending(lockres);
>> lockres->l_action = OCFS2_AST_ATTACH;
>> lockres_or_flags(lockres, OCFS2_LOCK_BUSY);
>> spin_unlock_irqrestore(&lockres->l_lock, flags);
>>
>> ocfs2_dlm_lock() finished and returned.
>> **and lockres_clear_pending(lockres, gen, osb);
>> request a lock on the same lockres M
>> It's blocked by nodeA, and a ast proxy
>> was send to A
>>
>> bast queued and flushed,before the ast was queued
>> then the ocfs2dc was scheduled
>> there is a chance to execute this code path:
>> ocfs2_downconvert_thread()
>> ocfs2_downconvert_thread_do_work()
>> ocfs2_blocking_ast()
>> ocfs2_process_blocked_lock()
>> ocfs2_unblock_lock()
>> spin_lock_irqsave(&lockres->l_lock, flags);
>> if (lockres->l_flags& OCFS2_LOCK_BUSY)
>> ret = ocfs2_prepare_cancel_convert(osb, lockres);
>> BUG_ON(lockres->l_action != OCFS2_AST_CONVERT&&
>> lockres->l_action != OCFS2_AST_DOWNCONVERT);
>> here trigger the BUG()
>>
>> Solution:
>> One possible solution for this is to remove the lockres_clear_pending
>> marked by 2 stars, and left this clear work to the ast function.In
>> this way could make sure the bast function wait for ast , let it
>> clear OCFS2_LOCK_BUSY and set OCFS2_LOCK_ATTACHED first, before enter
>> downconvert process.
>>
>>
>
next prev parent reply other threads:[~2012-02-22 0:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <xiaowei.hu@oracle.com>
2012-02-21 6:12 ` [Ocfs2-devel] Race condition between OCFS2 downconvert thread and ocfs2 cluster lock xiaowei.hu at oracle.com
2012-02-21 6:12 ` [Ocfs2-devel] [PATCH] fixing dlmglue race condition xiaowei.hu at oracle.com
2012-02-21 17:48 ` [Ocfs2-devel] Race condition between OCFS2 downconvert thread and ocfs2 cluster lock Sunil Mushran
2012-02-22 0:36 ` Xiaowei.hu [this message]
2012-02-22 0:45 ` Sunil Mushran
2012-02-22 0:58 ` Xiaowei.hu
2012-02-22 1:39 ` Sunil Mushran
2012-07-24 5:27 ` Xiaowei
2012-02-21 18:04 ` Sunil Mushran
2012-02-22 0:42 ` Xiaowei.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=4F44387E.7040502@oracle.com \
--to=xiaowei.hu@oracle.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).