* [PATCH linux-next] perf lock: use strscpy() is more robust and safer
@ 2022-09-22 1:32 cgel.zte
0 siblings, 0 replies; only message in thread
From: cgel.zte @ 2022-09-22 1:32 UTC (permalink / raw)
To: acme
Cc: mingo, mark.rutland, alexander.shishkin, jolsa, namhyung,
linux-perf-users, linux-kernel, ye xingchen, Zeal Robot
From: ye xingchen <ye.xingchen@zte.com.cn>
The implementation of strscpy() is more robust and safer.
That's now the recommended way to copy NUL terminated strings.
Reported-by: Zeal Robot <zealci@zte.com.cn>
Signed-off-by: ye xingchen <ye.xingchen@zte.com.cn>
---
tools/perf/builtin-lock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/builtin-lock.c b/tools/perf/builtin-lock.c
index 52a6a10a610c..b6837b7df110 100644
--- a/tools/perf/builtin-lock.c
+++ b/tools/perf/builtin-lock.c
@@ -949,7 +949,7 @@ static int lock_contention_caller(struct evsel *evsel, struct perf_sample *sampl
if (offset)
scnprintf(buf, size, "%s+%#lx", sym->name, offset);
else
- strlcpy(buf, sym->name, size);
+ strscpy(buf, sym->name, size);
return 0;
}
--
2.25.1
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2022-09-22 1:32 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-22 1:32 [PATCH linux-next] perf lock: use strscpy() is more robust and safer cgel.zte
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).