linux-staging.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dharanitharan R <dharanitharan725@gmail.com>
To: johan@kernel.org, elder@kernel.org, gregkh@linuxfoundation.org
Cc: greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
	Dharanitharan R <dharanitharan725@gmail.com>
Subject: [PATCH] staging: greybus: replace strncpy() with strlcpy() in firmware test tool
Date: Mon, 17 Nov 2025 06:50:03 +0000	[thread overview]
Message-ID: <20251117065003.7453-1-dharanitharan725@gmail.com> (raw)

The sample userspace firmware-management tool uses strncpy() to copy
firmware tags. strncpy() does not guarantee null-termination and can
leave buffers unterminated. For userspace code, strlcpy() is the
recommended safe alternative.

Replace all strncpy() calls with strlcpy().

Signed-off-by: Dharanitharan <dharanitharan725@gmail.com>
---
 .../greybus/Documentation/firmware/firmware.c      | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/drivers/staging/greybus/Documentation/firmware/firmware.c b/drivers/staging/greybus/Documentation/firmware/firmware.c
index 3b35ef6d4adb..224eb8f4e39c 100644
--- a/drivers/staging/greybus/Documentation/firmware/firmware.c
+++ b/drivers/staging/greybus/Documentation/firmware/firmware.c
@@ -63,8 +63,9 @@ static int update_intf_firmware(int fd)
 	intf_load.major = 0;
 	intf_load.minor = 0;
 
-	strncpy((char *)&intf_load.firmware_tag, firmware_tag,
-		GB_FIRMWARE_U_TAG_MAX_SIZE);
+    strlcpy(intf_load.firmware_tag, firmware_tag,
+       GB_FIRMWARE_U_TAG_MAX_SIZE);
+
 
 	ret = ioctl(fd, FW_MGMT_IOC_INTF_LOAD_AND_VALIDATE, &intf_load);
 	if (ret < 0) {
@@ -101,8 +102,9 @@ static int update_backend_firmware(int fd)
 	/* Get Backend Firmware Version */
 	printf("Getting Backend Firmware Version\n");
 
-	strncpy((char *)&backend_fw_info.firmware_tag, firmware_tag,
-		GB_FIRMWARE_U_TAG_MAX_SIZE);
+    strlcpy(backend_fw_info.firmware_tag, firmware_tag,
+       GB_FIRMWARE_U_TAG_MAX_SIZE);
+
 
 retry_fw_version:
 	ret = ioctl(fd, FW_MGMT_IOC_GET_BACKEND_FW, &backend_fw_info);
@@ -129,8 +131,8 @@ static int update_backend_firmware(int fd)
 	/* Try Backend Firmware Update over Unipro */
 	printf("Updating Backend Firmware\n");
 
-	strncpy((char *)&backend_update.firmware_tag, firmware_tag,
-		GB_FIRMWARE_U_TAG_MAX_SIZE);
+    strlcpy(backend_update.firmware_tag, firmware_tag,
+       GB_FIRMWARE_U_TAG_MAX_SIZE);
 
 retry_fw_update:
 	backend_update.status = 0;
-- 
2.43.0


             reply	other threads:[~2025-11-17  6:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17  6:50 Dharanitharan R [this message]
2025-11-17 12:33 ` [PATCH] staging: greybus: replace strncpy() with strlcpy() in firmware test tool Greg KH
2025-11-18  7:36 ` Dan Carpenter

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=20251117065003.7453-1-dharanitharan725@gmail.com \
    --to=dharanitharan725@gmail.com \
    --cc=elder@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=johan@kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).