From: Jiri Slaby <jirislaby@kernel.org>
To: xie.ludan@zte.com.cn, tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH linux-next] genirq: use sysfs_emit() instead of scnprintf().
Date: Mon, 17 Mar 2025 07:12:32 +0100 [thread overview]
Message-ID: <9c552d9a-2d46-4069-a9c4-35fab857bfc3@kernel.org> (raw)
In-Reply-To: <e177acba-24d3-4202-a0a8-92bfbfdf87e7@suse.cz>
On 17. 03. 25, 7:07, Jiri Slaby wrote:
> Hi,
>
> your e-mail is both multipart and base64 encoded :(. Pls fix up your
> setup first.
>
> On 15. 03. 25, 7:17, xie.ludan@zte.com.cn wrote:
>> From: XieLudan <xie.ludan@zte.com.cn>
>>
>>
>> Follow the advice in Documentation/filesystems/sysfs.rst:
>>
>> show() should only use sysfs_emit() or sysfs_emit_at() when formatting
>>
>> the value to be returned to user space.
>>
>>
>> Signed-off-by: XieLudan <xie.ludan@zte.com.cn>
>>
>> ---
>>
>> kernel/irq/irqdesc.c | 12 ++++++------
>>
>> 1 file changed, 6 insertions(+), 6 deletions(-)
>>
>>
>> diff --git a/kernel/irq/irqdesc.c b/kernel/irq/irqdesc.c
>>
>> index 287830739783..8ffe12fe5af6 100644
>>
>> --- a/kernel/irq/irqdesc.c
>>
>> +++ b/kernel/irq/irqdesc.c
>>
>> @@ -257,11 +257,11 @@ static ssize_t per_cpu_count_show(struct kobject
>> *kobj,
>>
>> for_each_possible_cpu(cpu) {
>>
>> unsigned int c = irq_desc_kstat_cpu(desc, cpu);
>>
>> -ret += scnprintf(buf + ret, PAGE_SIZE - ret, "%s%u", p, c);
>>
>> +ret += sysfs_emit(buf + ret, "%s%u", p, c);
>
> Well, so the PAGE_SIZE boundary is never checked for this stacking write
> now, right?
^^^ not really clear what I mean, so:
If you advance buf by ret every time, sysfs_emit() still would only
check if buf is not written more than "PAGE_SIZE" bytes. But the
original code performs this proper "PAGE_SIZE - ret" check.
> thanks,
--
js
suse labs
next prev parent reply other threads:[~2025-03-17 6:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-15 6:17 [PATCH linux-next] genirq: use sysfs_emit() instead of scnprintf() xie.ludan
2025-03-17 6:07 ` Jiri Slaby
2025-03-17 6:12 ` Jiri Slaby [this message]
2025-03-17 6:17 ` Jiri Slaby
-- strict thread matches above, loose matches on Subject: below --
2025-03-17 6:27 xie.ludan
2025-03-17 6:37 ` Jiri Slaby
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=9c552d9a-2d46-4069-a9c4-35fab857bfc3@kernel.org \
--to=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=xie.ludan@zte.com.cn \
/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