From: Xiubo Li <xiubli@redhat.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: jlayton@kernel.org, idryomov@gmail.com, viro@zeniv.linux.org.uk,
willy@infradead.org, vshankar@redhat.com,
ceph-devel@vger.kernel.org, arnd@arndb.de,
akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] fs/dcache: add d_compare() helper support
Date: Tue, 24 May 2022 09:46:34 +0800 [thread overview]
Message-ID: <2f43382d-3ab1-3562-c527-5cfef9ac069e@redhat.com> (raw)
In-Reply-To: <YovK86vEmOUUoBn6@bombadil.infradead.org>
On 5/24/22 1:57 AM, Luis Chamberlain wrote:
> On Thu, May 19, 2022 at 06:18:45PM +0800, Xiubo Li wrote:
>> Reviewed-by: Jeff Layton <jlayton@kernel.org>
>> Signed-off-by: Xiubo Li <xiubli@redhat.com>
>> ---
>> fs/dcache.c | 15 +++++++++++++++
>> include/linux/dcache.h | 2 ++
>> 2 files changed, 17 insertions(+)
>>
>> diff --git a/fs/dcache.c b/fs/dcache.c
>> index 93f4f5ee07bf..95a72f92a94b 100644
>> --- a/fs/dcache.c
>> +++ b/fs/dcache.c
>> @@ -2262,6 +2262,21 @@ static inline bool d_same_name(const struct dentry *dentry,
>> name) == 0;
>> }
>>
>> +/**
>> + * d_compare - compare dentry name with case-exact name
>> + * @parent: parent dentry
>> + * @dentry: the negative dentry that was passed to the parent's lookup func
>> + * @name: the case-exact name to be associated with the returned dentry
>> + *
>> + * Return: 0 if names are same, or 1
>> + */
>> +bool d_compare(const struct dentry *parent, const struct dentry *dentry,
>> + const struct qstr *name)
>> +{
>> + return !d_same_name(dentry, parent, name);
> What's wrong with d_same_name()? Why introduce a whole new operation
> and export it when you the same prototype except first and second
> argument moved with an even more confusing name?
Sounds resonable, will export the d_same_name instead.
>> +}
>> +EXPORT_SYMBOL(d_compare);
> New symbols should go with EXPORT_SYMBOL_GPL() instead.
Not familiar with the story about this, before I checked the Doc and
didn't find any where says we must use it and just followed what recent
commits did.
If this is what we should use I will switch to it in the next version.
Thanks
-- Xiubo
>
> Luis
>
next prev parent reply other threads:[~2022-05-24 1:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 10:18 [PATCH v5 0/2] ceph: wait async unlink to finish Xiubo Li
2022-05-19 10:18 ` [PATCH v5 1/2] fs/dcache: add d_compare() helper support Xiubo Li
2022-05-23 17:57 ` Luis Chamberlain
2022-05-23 18:09 ` Jeff Layton
2022-05-24 1:46 ` Xiubo Li [this message]
2022-05-23 20:11 ` Matthew Wilcox
2022-05-24 1:32 ` Xiubo Li
2022-05-19 10:18 ` [PATCH v5 2/2] ceph: wait the first reply of inflight async unlink Xiubo Li
2022-05-19 11:30 ` Jeff Layton
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=2f43382d-3ab1-3562-c527-5cfef9ac069e@redhat.com \
--to=xiubli@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=vshankar@redhat.com \
--cc=willy@infradead.org \
/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).