From: piaojun <piaojun@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [patch 1/2] ocfs2/dlm: protect 'tracking_list' by 'track_lock'
Date: Tue, 26 Sep 2017 08:39:31 +0800 [thread overview]
Message-ID: <59C9A1C3.4060502@huawei.com> (raw)
In-Reply-To: <a3302b2c-3492-5d77-ffe1-af630a1a8028@gmail.com>
On 2017/9/25 18:35, Joseph Qi wrote:
>
>
> On 17/9/23 11:39, piaojun wrote:
>> 'dlm->tracking_list' need to be protected by 'dlm->track_lock'.
>>
>> Signed-off-by: Jun Piao <piaojun@huawei.com>
>> Reviewed-by: Alex Chen <alex.chen@huawei.com>
>> ---
>> fs/ocfs2/dlm/dlmdomain.c | 7 ++++++-
>> fs/ocfs2/dlm/dlmmaster.c | 4 ++--
>> 2 files changed, 8 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/ocfs2/dlm/dlmdomain.c b/fs/ocfs2/dlm/dlmdomain.c
>> index a2b19fb..b118525 100644
>> --- a/fs/ocfs2/dlm/dlmdomain.c
>> +++ b/fs/ocfs2/dlm/dlmdomain.c
>> @@ -726,12 +726,17 @@ void dlm_unregister_domain(struct dlm_ctxt *dlm)
>> }
>>
>> /* This list should be empty. If not, print remaining lockres */
>> + spin_lock(&dlm->track_lock);
>> if (!list_empty(&dlm->tracking_list)) {
>> mlog(ML_ERROR, "Following lockres' are still on the "
>> "tracking list:\n");
>> - list_for_each_entry(res, &dlm->tracking_list, tracking)
>> + list_for_each_entry(res, &dlm->tracking_list, tracking) {
>> + spin_unlock(&dlm->track_lock);
>
> Um... If we unlock here, the iterator still has chance to be corrupted.
>
> Thanks,
> Joseph
>
we don't need care much about the corrupted 'tracking_list' because we
have already picked up 'res' from 'tracking_list'. then we will get
'track_lock' again to prevent 'tracking_list' from being corrupted. but
I'd better make sure that 'res' is not NULL before printing, just like:
list_for_each_entry(res, &dlm->tracking_list, tracking) {
spin_unlock(&dlm->track_lock);
if (res)
dlm_print_one_lock_resource(res);
spin_lock(&dlm->track_lock);
}
Thanks
Jun
>> dlm_print_one_lock_resource(res);
>> + spin_lock(&dlm->track_lock);
>> + }
>> }
>> + spin_unlock(&dlm->track_lock);
>>
>> dlm_mark_domain_leaving(dlm);
>> dlm_leave_domain(dlm);
>> diff --git a/fs/ocfs2/dlm/dlmmaster.c b/fs/ocfs2/dlm/dlmmaster.c
>> index 3e04279..44e7d18 100644
>> --- a/fs/ocfs2/dlm/dlmmaster.c
>> +++ b/fs/ocfs2/dlm/dlmmaster.c
>> @@ -589,9 +589,9 @@ static void dlm_init_lockres(struct dlm_ctxt *dlm,
>>
>> res->last_used = 0;
>>
>> - spin_lock(&dlm->spinlock);
>> + spin_lock(&dlm->track_lock);
>> list_add_tail(&res->tracking, &dlm->tracking_list);
>> - spin_unlock(&dlm->spinlock);
>> + spin_unlock(&dlm->track_lock);
>>
>> memset(res->lvb, 0, DLM_LVB_LEN);
>> memset(res->refmap, 0, sizeof(res->refmap));
>>
> .
>
next prev parent reply other threads:[~2017-09-26 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 3:39 [Ocfs2-devel] [patch 1/2] ocfs2/dlm: protect 'tracking_list' by 'track_lock' piaojun
2017-09-25 10:35 ` Joseph Qi
2017-09-26 0:39 ` piaojun [this message]
2017-09-27 1:32 ` Joseph Qi
2017-09-27 2:10 ` piaojun
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=59C9A1C3.4060502@huawei.com \
--to=piaojun@huawei.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