* [PATCH] staging: wlan-ng: replace strncpy() with strscpy()
@ 2023-10-16 6:39 Calvince Otieno
2023-10-16 8:49 ` Dan Carpenter
0 siblings, 1 reply; 2+ messages in thread
From: Calvince Otieno @ 2023-10-16 6:39 UTC (permalink / raw)
To: gustavo, outreachy
Cc: Greg Kroah-Hartman, linux-staging, linux-kernel, Calvince Otieno,
Dan Carpenter
Checkpatch suggests the use of strscpy() instead of strncpy().
The advantages are that it always adds a NUL terminator and it prevents
a read overflow if the src string is not properly terminated. One
potential disadvantage is that it doesn't zero pad the string like
strncpy() does.
In this code, strscpy() and strncpy() are equivalent and it does not
affect runtime behavior. The string is zeroed on the line before
using memset(). The resulting string was always NUL terminated and
PRISM2_USB_FWFILE is string literal "prism2_ru.fw" so it's NUL
terminated.
However, even though using strscpy() does not fix any bugs, it's
still nicer and makes checkpatch happy.
Signed-off-by: Calvince Otieno <calvncce@gmail.com>
---
Previous Patch Versions:
- Earlier patch versions had issues with whitespace, preventing correct
application. This is a reroll of those previous versions.
- Versions v2 through v6 focused on improving the clarity of the commit
message. There were no code changes in these patch versions.
drivers/staging/wlan-ng/prism2fw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wlan-ng/prism2fw.c b/drivers/staging/wlan-ng/prism2fw.c
index 5d03b2b9aab4..3ccd11041646 100644
--- a/drivers/staging/wlan-ng/prism2fw.c
+++ b/drivers/staging/wlan-ng/prism2fw.c
@@ -725,7 +725,7 @@ static int plugimage(struct imgchunk *fchunk, unsigned int nfchunks,
if (j == -1) { /* plug the filename */
memset(dest, 0, s3plug[i].len);
- strncpy(dest, PRISM2_USB_FWFILE, s3plug[i].len - 1);
+ strscpy(dest, PRISM2_USB_FWFILE, s3plug[i].len);
} else { /* plug a PDR */
memcpy(dest, &pda->rec[j]->data, s3plug[i].len);
}
--
2.34.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] staging: wlan-ng: replace strncpy() with strscpy()
2023-10-16 6:39 [PATCH] staging: wlan-ng: replace strncpy() with strscpy() Calvince Otieno
@ 2023-10-16 8:49 ` Dan Carpenter
0 siblings, 0 replies; 2+ messages in thread
From: Dan Carpenter @ 2023-10-16 8:49 UTC (permalink / raw)
To: Calvince Otieno
Cc: gustavo, outreachy, Greg Kroah-Hartman, linux-staging,
linux-kernel
On Mon, Oct 16, 2023 at 09:39:33AM +0300, Calvince Otieno wrote:
> Checkpatch suggests the use of strscpy() instead of strncpy().
> The advantages are that it always adds a NUL terminator and it prevents
> a read overflow if the src string is not properly terminated. One
> potential disadvantage is that it doesn't zero pad the string like
> strncpy() does.
> In this code, strscpy() and strncpy() are equivalent and it does not
> affect runtime behavior. The string is zeroed on the line before
> using memset(). The resulting string was always NUL terminated and
> PRISM2_USB_FWFILE is string literal "prism2_ru.fw" so it's NUL
> terminated.
> However, even though using strscpy() does not fix any bugs, it's
> still nicer and makes checkpatch happy.
>
> Signed-off-by: Calvince Otieno <calvncce@gmail.com>
> ---
> Previous Patch Versions:
> - Earlier patch versions had issues with whitespace, preventing correct
> application. This is a reroll of those previous versions.
>
> - Versions v2 through v6 focused on improving the clarity of the commit
> message. There were no code changes in these patch versions.
You forgot to put v6 in the subject... But it looks okay now.
Reviewed-by: Dan Carpenter <dan.carpenter@linaro.org>
regards,
dan carpenter
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-10-16 8:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-10-16 6:39 [PATCH] staging: wlan-ng: replace strncpy() with strscpy() Calvince Otieno
2023-10-16 8:49 ` Dan Carpenter
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox