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: set OCFS2_LOCK_BLOCKED properly
Date: Tue, 05 Jan 2010 09:50:33 -0800	[thread overview]
Message-ID: <4B437BE9.7090803@oracle.com> (raw)
In-Reply-To: <201001051707.o05Gxath022586@acsinet15.oracle.com>

woah... this looks like a good catch.

Mark?

Wengang Wang wrote:
> for most cases ocfs2_generic_handle_bast() return 1 meaning that some down-
> converting work should be done. but when it return 0, the OCFS2_LOCK_BLOCKED is
> set inproperly.
> OCFS2_LOCK_BLOCKED is cleared in a down-convertion(dc) is done. if no dc is needed
> any more(done by another lock request queued before this one), OCFS2_LOCK_BLOCKED
> stays there unexpectly.
>
> the fix is that setting that flag when dc(s) is really needed.
>
> Signed-off-by: Wengang Wang <wen.gang.wang@oracle.com>
> ---
>  fs/ocfs2/dlmglue.c |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ocfs2/dlmglue.c b/fs/ocfs2/dlmglue.c
> index c5e4a49..e18eadf 100644
> --- a/fs/ocfs2/dlmglue.c
> +++ b/fs/ocfs2/dlmglue.c
> @@ -907,8 +907,6 @@ static int ocfs2_generic_handle_bast(struct ocfs2_lock_res *lockres,
>  
>  	assert_spin_locked(&lockres->l_lock);
>  
> -	lockres_or_flags(lockres, OCFS2_LOCK_BLOCKED);
> -
>  	if (level > lockres->l_blocking) {
>  		/* only schedule a downconvert if we haven't already scheduled
>  		 * one that goes low enough to satisfy the level we're
> @@ -921,6 +919,9 @@ static int ocfs2_generic_handle_bast(struct ocfs2_lock_res *lockres,
>  		lockres->l_blocking = level;
>  	}
>  
> +	if (needs_downconvert)
> +		lockres_or_flags(lockres, OCFS2_LOCK_BLOCKED);
> +		
>  	mlog_exit(needs_downconvert);
>  	return needs_downconvert;
>  }
>   

  reply	other threads:[~2010-01-05 17:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 17:05 [Ocfs2-devel] [PATCH] ocfs2: set OCFS2_LOCK_BLOCKED properly Wengang Wang
2010-01-05 17:50 ` Sunil Mushran [this message]
2010-01-07  1:03   ` Mark Fasheh
2010-01-07  1:46     ` Joel Becker
2010-01-07  2:10     ` Wengang Wang
2010-01-07  2:50       ` Mark Fasheh

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=4B437BE9.7090803@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.