From: Chen Zhou <chenzhou10@huawei.com>
To: Michael Ellerman <mpe@ellerman.id.au>, <benh@kernel.crashing.org>,
<paulus@samba.org>
Cc: <linuxppc-dev@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
"Nicolai Stange" <nicstange@gmail.com>,
Julia Lawall <Julia.Lawall@lip6.fr>
Subject: Re: [PATCH] powerpc/setup_64: use DEFINE_DEBUGFS_ATTRIBUTE to define fops_rfi_flush
Date: Thu, 19 Dec 2019 09:20:19 +0800 [thread overview]
Message-ID: <69722925-d0ab-ab7e-022f-c901ead3989a@huawei.com> (raw)
In-Reply-To: <8736dhoq0j.fsf@mpe.ellerman.id.au>
Hi Michael,
On 2019/12/18 19:02, Michael Ellerman wrote:
> Chen Zhou <chenzhou10@huawei.com> writes:
>> Use DEFINE_DEBUGFS_ATTRIBUTE rather than DEFINE_SIMPLE_ATTRIBUTE for
>> debugfs files.
>>
>> Semantic patch information:
>> Rationale: DEFINE_SIMPLE_ATTRIBUTE + debugfs_create_file()
>> imposes some significant overhead as compared to
>> DEFINE_DEBUGFS_ATTRIBUTE + debugfs_create_file_unsafe().
>
> I know you didn't write this text, but these change logs are not great.
> It doesn't really explain why you're doing it. And it is alarming that
> you're converting *to* a function with "unsafe" in the name.
>
> The commit that added the script:
>
> 5103068eaca2 ("debugfs, coccinelle: check for obsolete DEFINE_SIMPLE_ATTRIBUTE() usage")
>
> Has a bit more explanation.
>
> Maybe something like this:
>
> In order to protect against file removal races, debugfs files created via
> debugfs_create_file() are wrapped by a struct file_operations at their
> opening.
>
> If the original struct file_operations is known to be safe against removal
> races already, the proxy creation may be bypassed by creating the files
> using DEFINE_DEBUGFS_ATTRIBUTE() and debugfs_create_file_unsafe().
>
>
> The part that's not explained is why this file is "known to be safe
> against removal races already"?
>
> It also seems this conversion will make the file no longer seekable,
> because DEFINE_SIMPLE_ATTRIBUTE() uses generic_file_llseek() whereas
> DEFINE_DEBUGFS_ATTRIBUTE() uses no_llseek.
>
> That is probably fine, but should be mentioned.
Thanks for your explanation. This part indeed should be mentioned.
Chen Zhou
>
> cheers
>
>> Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
>> ---
>> arch/powerpc/kernel/setup_64.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/powerpc/kernel/setup_64.c b/arch/powerpc/kernel/setup_64.c
>> index 6104917..4b9fbb2 100644
>> --- a/arch/powerpc/kernel/setup_64.c
>> +++ b/arch/powerpc/kernel/setup_64.c
>> @@ -956,11 +956,11 @@ static int rfi_flush_get(void *data, u64 *val)
>> return 0;
>> }
>>
>> -DEFINE_SIMPLE_ATTRIBUTE(fops_rfi_flush, rfi_flush_get, rfi_flush_set, "%llu\n");
>> +DEFINE_DEBUGFS_ATTRIBUTE(fops_rfi_flush, rfi_flush_get, rfi_flush_set, "%llu\n");
>>
>> static __init int rfi_flush_debugfs_init(void)
>> {
>> - debugfs_create_file("rfi_flush", 0600, powerpc_debugfs_root, NULL, &fops_rfi_flush);
>> + debugfs_create_file_unsafe("rfi_flush", 0600, powerpc_debugfs_root, NULL, &fops_rfi_flush);
>> return 0;
>> }
>> device_initcall(rfi_flush_debugfs_init);
>> --
>> 2.7.4
>
> .
>
prev parent reply other threads:[~2019-12-19 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 2:08 Chen Zhou
2019-12-18 11:02 ` Michael Ellerman
2019-12-19 1:20 ` Chen Zhou [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=69722925-d0ab-ab7e-022f-c901ead3989a@huawei.com \
--to=chenzhou10@huawei.com \
--cc=Julia.Lawall@lip6.fr \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nicstange@gmail.com \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®