ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Wengang Wang <wen.gang.wang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2/dlm: remove potential deadlock
Date: Mon, 21 Jun 2010 13:31:39 +0800	[thread overview]
Message-ID: <20100621053139.GA2809@laptop.us.oracle.com> (raw)
In-Reply-To: <201006160654.o5G1s1E0006164@acsinet15.oracle.com>

Why atomic operations on dlm_refs need spinlock's protect?

        /* NOTE: Next three are protected by dlm_domain_lock */
        struct kref dlm_refs;
        enum dlm_ctxt_state dlm_state;
        unsigned int num_joins;

regards,
wengang.

On 10-06-16 14:52, Wengang Wang wrote:
> When we need to take both dlm_domain_lock and dlm->spinlock, we should take
> them in order of:
> dlm_domain_lock then dlm->spinlock.
> 
> There is pathes disobey this order. That is calling dlm_lockres_put with dlm->
> spinlock held. dlm_lockres_put() finally calls dlm_put() which take
> dlm_domain_lock.
> 
> The fix is moving the locking on dlm_domain_lock to dlm_ctxt_release() from
> dlm_put(). dlm_ctxt_release() is only called on the release of the last
> reference. Any path should not be holding dlm->spinlock when dropping the "last"
> reference.
> 
> Signed-off-by: Wengang Wang <wen.gang.wang@oracle.com>
> ---
>  fs/ocfs2/dlm/dlmdomain.c |   12 ++++--------
>  1 files changed, 4 insertions(+), 8 deletions(-)
> 
> diff --git a/fs/ocfs2/dlm/dlmdomain.c b/fs/ocfs2/dlm/dlmdomain.c
> index ab82add..754baf2 100644
> --- a/fs/ocfs2/dlm/dlmdomain.c
> +++ b/fs/ocfs2/dlm/dlmdomain.c
> @@ -321,28 +321,24 @@ static void dlm_ctxt_release(struct kref *kref)
>  
>  	dlm = container_of(kref, struct dlm_ctxt, dlm_refs);
>  
> +	if (spin_is_locked(&dlm->spinlock))
> +		BUG();
>  	BUG_ON(dlm->num_joins);
>  	BUG_ON(dlm->dlm_state == DLM_CTXT_JOINED);
>  
> +	spin_lock(&dlm_domain_lock);
>  	/* we may still be in the list if we hit an error during join. */
>  	list_del_init(&dlm->list);
> -
>  	spin_unlock(&dlm_domain_lock);
>  
> -	mlog(0, "freeing memory from domain %s\n", dlm->name);
> -
>  	wake_up(&dlm_domain_events);
> -
> +	mlog(0, "freeing memory from domain %s\n", dlm->name);
>  	dlm_free_ctxt_mem(dlm);
> -
> -	spin_lock(&dlm_domain_lock);
>  }
>  
>  void dlm_put(struct dlm_ctxt *dlm)
>  {
> -	spin_lock(&dlm_domain_lock);
>  	kref_put(&dlm->dlm_refs, dlm_ctxt_release);
> -	spin_unlock(&dlm_domain_lock);
>  }
>  
>  static void __dlm_get(struct dlm_ctxt *dlm)
> -- 
> 1.6.6.1
> 
> 
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-devel

  reply	other threads:[~2010-06-21  5:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16  6:52 [Ocfs2-devel] [PATCH] ocfs2/dlm: remove potential deadlock Wengang Wang
2010-06-21  5:31 ` Wengang Wang [this message]
2010-06-21  7:33   ` Tao Ma
2010-06-21 13:44     ` Wengang Wang
2010-06-21 13:20 ` Wengang Wang

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=20100621053139.GA2809@laptop.us.oracle.com \
    --to=wen.gang.wang@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).