From: Waiman Long <llong@redhat.com>
To: Thorsten Blum <thorsten.blum@linux.dev>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] locking/lockdep: Replace snprintf with strscpy in seq_stats
Date: Mon, 26 Jan 2026 22:42:49 -0500 [thread overview]
Message-ID: <8f74c94a-3d53-475a-85ff-571c00029a1d@redhat.com> (raw)
In-Reply-To: <20260126235456.430591-2-thorsten.blum@linux.dev>
On 1/26/26 6:54 PM, Thorsten Blum wrote:
> Replace snprintf("%s", ...) with the faster and more direct strscpy().
>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
> kernel/locking/lockdep_proc.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/locking/lockdep_proc.c b/kernel/locking/lockdep_proc.c
> index 1916db9aa46b..e458fa258d05 100644
> --- a/kernel/locking/lockdep_proc.c
> +++ b/kernel/locking/lockdep_proc.c
> @@ -19,6 +19,7 @@
> #include <linux/debug_locks.h>
> #include <linux/vmalloc.h>
> #include <linux/sort.h>
> +#include <linux/string.h>
> #include <linux/uaccess.h>
> #include <asm/div64.h>
>
> @@ -488,9 +489,9 @@ static void seq_stats(struct seq_file *m, struct lock_stat_data *data)
> const char *key_name;
>
> key_name = __get_key_name(ckey, str);
> - snprintf(name, namelen, "%s", key_name);
> + strscpy(name, key_name, namelen);
> } else {
> - snprintf(name, namelen, "%s", cname);
> + strscpy(name, cname, namelen);
> }
> rcu_read_unlock_sched();
>
Reviewed-by: Waiman Long <longman@redhat.com>
prev parent reply other threads:[~2026-01-27 3:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 23:54 [PATCH] locking/lockdep: Replace snprintf with strscpy in seq_stats Thorsten Blum
2026-01-27 3:42 ` Waiman Long [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=8f74c94a-3d53-475a-85ff-571c00029a1d@redhat.com \
--to=llong@redhat.com \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=thorsten.blum@linux.dev \
--cc=will@kernel.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