From: wengang wang <wen.gang.wang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Re: [PATCH] ocfs2_dlm: add spinlock protection before __dlm_print_one_lock_resource is called
Date: Tue Apr 17 20:41:48 2007 [thread overview]
Message-ID: <46259387.5040002@oracle.com> (raw)
In-Reply-To: <46258EB6.3010406@oracle.com>
same problem happens on dlm_deref_lockres_worker(1.2.5 and 1.2.4) and
dlm_deref_lockres_handler(1.2.4 only)
fix is the same.
wengang wang wrote:
> ocfs2_dlm: add spinlock protection per __dlm_print_one_lock_resource
> calling
>
> In dlm_convert_lock_handler(), in case of !lock,
> __dlm_print_one_lock_resource is called. __dlm_print_one_lock_resource
> needs protection of spinlock on res->spinlock. current source lost
> that protection.
> use dlm_print_one_lock_resource instead of __dlm_print_one_lock_resource.
>
> Signed-off-by: wengang wang <wen.gang.wang@oracle.com>
>
> Index: ocfs2-1.2.5/fs/ocfs2/dlm/dlmconvert.c
>
> ===================================================================
> --- ocfs2-1.2.5/fs/ocfs2/dlm/dlmconvert.c.orig 2007-04-18
> 11:15:36.000000000 -0400
> +++ ocfs2-1.2.5/fs/ocfs2/dlm/dlmconvert.c 2007-04-18
> 11:16:00.000000000 -0400
> @@ -490,7 +490,7 @@
> "cookie=%u:%llu\n",
>
> dlm_get_lock_cookie_node(be64_to_cpu(cnv->cookie)),
>
> dlm_get_lock_cookie_seq(be64_to_cpu(cnv->cookie)));
> - __dlm_print_one_lock_resource(res);
> + dlm_print_one_lock_resource(res);
> goto leave;
> }
>
>
>
>
--
Wengang Wang
Member of Technical Staff
Oracle China Development Center
Open Source Technologies Development
Tel: +86 10 8278 6265
Mobile: +86 13381078925
prev parent reply other threads:[~2007-04-17 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 2:41 [Ocfs2-devel] a patch on ocfs2 wengang wang
2007-04-17 9:51 ` Sunil Mushran
2007-04-17 20:21 ` [Ocfs2-devel] [PATCH] ocfs2_dlm: add spinlock protection before __dlm_print_one_lock_resource is called wengang wang
2007-04-17 20:41 ` wengang wang [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=46259387.5040002@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 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.