From: "yukuai (C)" <yukuai3@huawei.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: <gregkh@linuxfoundation.org>, <rafael@kernel.org>,
<viro@zeniv.linux.org.uk>, <rostedt@goodmis.org>,
<oleg@redhat.com>, <mchehab+samsung@kernel.org>, <corbet@lwn.net>,
<tytso@mit.edu>, <jmorris@namei.org>,
<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<zhengbin13@huawei.com>, <yi.zhang@huawei.com>,
<chenxiang66@hisilicon.com>, <xiexiuqi@huawei.com>
Subject: Re: [PATCH V2 1/3] dcache: add a new enum type for 'dentry_d_lock_class'
Date: Sat, 30 Nov 2019 15:53:10 +0800 [thread overview]
Message-ID: <e2e7c9f1-7152-1d74-c434-c2c4d57d0422@huawei.com> (raw)
In-Reply-To: <20191130034339.GI20752@bombadil.infradead.org>
On 2019/11/30 11:43, Matthew Wilcox wrote:
> On Sat, Nov 30, 2019 at 10:02:23AM +0800, yu kuai wrote:
>> However, a single 'DENTRY_D_LOCK_NESTED' may not be enough if more than
>> two dentry are involed. So, add in 'DENTRY_D_LOCK_NESTED_TWICE'.
>
> No. These need meaningful names. Indeed, I think D_LOCK_NESTED is
> a terrible name.
>
> Looking at the calls:
>
> $ git grep -n nested.*d_lock fs
> fs/autofs/expire.c:82: spin_lock_nested(&child->d_lock, DENTRY_D_LOCK_NESTED);
> fs/dcache.c:619: spin_lock_nested(&dentry->d_lock, DENTRY_D_LOCK_NESTED);
> fs/dcache.c:1086: spin_lock_nested(&dentry->d_lock, DENTRY_D_LOCK_NESTED);
> fs/dcache.c:1303: spin_lock_nested(&dentry->d_lock, DENTRY_D_LOCK_NESTED);
> fs/dcache.c:2822: spin_lock_nested(&old_parent->d_lock, DENTRY_D_LOCK_NESTED);
> fs/dcache.c:2827: spin_lock_nested(&target->d_parent->d_lock,
> fs/dcache.c:2830: spin_lock_nested(&dentry->d_lock, 2);
> fs/dcache.c:2831: spin_lock_nested(&target->d_lock, 3);
> fs/dcache.c:3121: spin_lock_nested(&dentry->d_lock, DENTRY_D_LOCK_NESTED);
> fs/libfs.c:112: spin_lock_nested(&d->d_lock, DENTRY_D_LOCK_NESTED);
> fs/libfs.c:341: spin_lock_nested(&child->d_lock, DENTRY_D_LOCK_NESTED);
> fs/notify/fsnotify.c:129: spin_lock_nested(&child->d_lock, DENTRY_D_LOCK_NESTED);
>
> Most of these would be well-expressed by DENTRY_D_LOCK_CHILD.
>
> The exception is __d_move() where I think we should actually name the
> different lock classes instead of using a bare '2' and '3'. Something
> like this, perhaps:
>
Thanks for looking into this, do you mind if I replace your patch with
the first two patches in the patchset?
Yu Kuai
next prev parent reply other threads:[~2019-11-30 7:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-30 2:02 [PATCH V2 0/3] fix potential infinite loop in debugfs_remove_recursive yu kuai
2019-11-30 2:02 ` [PATCH V2 1/3] dcache: add a new enum type for 'dentry_d_lock_class' yu kuai
2019-11-30 3:43 ` Matthew Wilcox
2019-11-30 7:53 ` yukuai (C) [this message]
2019-11-30 19:36 ` Matthew Wilcox
2019-12-08 19:11 ` Al Viro
2019-12-11 15:55 ` David Hildenbrand
2019-12-11 18:46 ` Al Viro
2019-12-11 19:18 ` David Hildenbrand
2019-12-11 19:27 ` David Hildenbrand
2019-11-30 2:02 ` [PATCH 2/3] fs/libfs.c: use 'spin_lock_nested' when taking 'd_lock' for dentry in simple_empty yu kuai
2019-11-30 2:02 ` [PATCH 3/3] debugfs: fix potential infinite loop in debugfs_remove_recursive yu kuai
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=e2e7c9f1-7152-1d74-c434-c2c4d57d0422@huawei.com \
--to=yukuai3@huawei.com \
--cc=chenxiang66@hisilicon.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=oleg@redhat.com \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=xiexiuqi@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=zhengbin13@huawei.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).