All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2/dlm: queue ast in lockres->spinlock
Date: Tue, 30 Nov 2010 21:33:32 -0800	[thread overview]
Message-ID: <4CF5DE2C.2090807@oracle.com> (raw)
In-Reply-To: <20101201025218.GA3709@laptop.jp.oracle.com>

On 11/30/2010 06:52 PM, Wengang Wang wrote:
> First I have to say that the scenario is in my thought only, no tcpdump
> shows that. Only the node C wanting a PR is the truth from the vmcore.
>
> Let's consider this situation:
>
> The create lock(CL) is for a PR;
> the up convert(UC) is PR->EX;
> there is an existing PR granted for another node(say node D) before the UC comes
>
> The UC comes. Because of the existing PR, the UC lock is moved to converting list.
> dlm_thread takes care it later.
> The CL comes. no conflict found(see dlm_can_grant_new_lock, convert_type not
> checked there). so it's not added to blocked list.
>
> Seems the above scenario can trigger a BAST before AST.

dlm_can_grant_new_lock() should be looking at convert_type also and
add the lock to the blocked list in this case.

This is not just to plug this hole but is as per the spec.

  reply	other threads:[~2010-12-01  5:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 15:48 [Ocfs2-devel] [PATCH] ocfs2/dlm: queue ast in lockres->spinlock Wengang Wang
2010-11-30 19:24 ` Sunil Mushran
2010-12-01  2:52   ` Wengang Wang
2010-12-01  5:33     ` Sunil Mushran [this message]
2010-12-01  6:16       ` Wengang Wang
2010-12-01  6:24         ` Sunil Mushran

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=4CF5DE2C.2090807@oracle.com \
    --to=sunil.mushran@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 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.