linux-kernel - Re: [PATCH] kernel/sched: use seq_putc instead of seq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <xhsmho7bgdcrt.mognet@vschneid-thinkpadt14sgen2i.remote.csb>
Date: Thu, 14 Mar 2024 17:00:22 +0100
From: Valentin Schneider <vschneid@...hat.com>
To: Maxim Moskalets <maximmosk4@...il.com>, Ingo Molnar <mingo@...hat.com>,
 Peter Zijlstra <peterz@...radead.org>, Juri Lelli <juri.lelli@...hat.com>,
 Vincent Guittot <vincent.guittot@...aro.org>, Dietmar Eggemann
 <dietmar.eggemann@....com>, Steven Rostedt <rostedt@...dmis.org>, Ben
 Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>, Daniel Bristot
 de Oliveira <bristot@...hat.com>, linux-kernel@...r.kernel.org
Cc: Maxim Moskalets <Maxim.Moskalets@...persky.com>
Subject: Re: [PATCH] kernel/sched: use seq_putc instead of seq_puts

On 03/03/24 14:05, Maxim Moskalets wrote:
> Using seq_putc for newline characters is faster and more appropriate
> than seq_puts, since only one character is passed and there is no need
> to use a more powerful and less fast function
>

Why not, but then why not do this treewide? A quick grep shows ~340 such
sites. That makes for a fairly easy coccinelle patch.