[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221020091312.398909-1-cui.jinpeng2@zte.com.cn>
Date: Thu, 20 Oct 2022 09:13:12 +0000
From: cuijinpeng666@...il.com
To: jstultz@...gle.com, tglx@...utronix.de
Cc: sboyd@...nel.org, linux-kernel@...r.kernel.org,
Jinpeng Cui <cui.jinpeng2@....com.cn>,
Zeal Robot <zaelci@....com.cn>
Subject: [PATCH linux-next] clocksource: Use strscpy() instead of strlcpy()
From: Jinpeng Cui <cui.jinpeng2@....com.cn>
The implementation of strscpy() is more robust and safer.
Reported-by: Zeal Robot <zaelci@....com.cn>
Signed-off-by: Jinpeng Cui <cui.jinpeng2@....com.cn>
---
kernel/time/clocksource.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/clocksource.c b/kernel/time/clocksource.c
index dcaf38c06216..a3e7edfbb3c2 100644
--- a/kernel/time/clocksource.c
+++ b/kernel/time/clocksource.c
@@ -1461,7 +1461,7 @@ static int __init boot_override_clocksource(char* str)
{
mutex_lock(&clocksource_mutex);
if (str)
- strlcpy(override_name, str, sizeof(override_name));
+ strscpy(override_name, str, sizeof(override_name));
mutex_unlock(&clocksource_mutex);
return 1;
}
--
2.25.1
Powered by blists - more mailing lists