From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: ny <nygameemail@163.com>
Cc: peterz@infradead.org, mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tools: Replace strlcpy with strscpy
Date: Tue, 13 Jan 2026 17:06:51 -0300 [thread overview]
Message-ID: <aWal26MDoKcxPEn4@x1> (raw)
In-Reply-To: <20251209125915.305793-1-nygameemail@163.com>
On Tue, Dec 09, 2025 at 12:59:15PM +0000, ny wrote:
> Replace the deprecated strlcpy function with the preferred strscpy
> function in tools/perf/util/machine.c.
>
> strlcpy is deprecated and should be replaced with strscpy according
> to kernel best practices. The strscpy function is safer and is the
> recommended replacement.
Take a look at this:
acme@number:~/git/perf-tools-next$ git grep strscpy tools/
tools/include/linux/string.h:#define strscpy strcpy
tools/testing/selftests/net/ovpn/ovpn-cli.c:#define strscpy strncpy
tools/testing/selftests/net/ovpn/ovpn-cli.c: strscpy(ovpn->ifname, argv[2], IFNAMSIZ - 1);
tools/testing/selftests/user_events/abi_test.c: /* strscpy is not available, use snprintf */
acme@number:~/git/perf-tools-next$
:-)
srcscpy() thus seems to be only available in the kernel sources, not for
tools/, that would be another project.
- Arnaldo
> Signed-off-by: ny <nygameemail@163.com>
> ---
> tools/perf/util/machine.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/machine.c b/tools/perf/util/machine.c
> index 841b711d9..8786764e2 100644
> --- a/tools/perf/util/machine.c
> +++ b/tools/perf/util/machine.c
> @@ -1052,7 +1052,7 @@ int machine__create_extra_kernel_map(struct machine *machine,
>
> kmap = map__kmap(map);
>
> - strlcpy(kmap->name, xm->name, KMAP_NAME_LEN);
> + strscpy(kmap->name, xm->name, KMAP_NAME_LEN);
>
> err = maps__insert(machine__kernel_maps(machine), map);
>
> --
> 2.43.0
prev parent reply other threads:[~2026-01-13 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 12:59 [PATCH] perf tools: Replace strlcpy with strscpy ny
2026-01-13 20:06 ` Arnaldo Carvalho de Melo [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=aWal26MDoKcxPEn4@x1 \
--to=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nygameemail@163.com \
--cc=peterz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.