From: Mariia Nikitash <nikitash.mariiaw@gmail.com>
To: arend.vanspriel@broadcom.com
Cc: linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
brcm80211-dev-list.pdl@broadcom.com,
linux-kernel@vger.kernel.org, morbo@google.com, kees@kernel.org,
justinstitt@google.com, codemender-patching+linux@google.com,
Mariia Nikitash <nikitash.mariiaw@gmail.com>
Subject: [PATCH] wifi: brcmfmac: Replace strlcat() with snprintf() in brcmf_fw_alloc_request()
Date: Tue, 13 Oct 2026 17:55:52 -0700 [thread overview]
Message-ID: <20261014005553.71803-1-nikitash.mariiaw@gmail.com> (raw)
From: Bill Wendling <morbo@google.com>
brcmf_fw_alloc_request() constructs firmware file paths by chaining
strscpy() and multiple strlcat() calls for the module parameter path,
separator, base name, and extension.
In preparation for removing the deprecated strlcat() API[1], format the
complete firmware path in a single snprintf() call.
Link: https://github.com/KSPP/linux/issues/370 [1]
Cc: codemender-patching+linux@google.com
Assisted-by: LLM
Signed-off-by: Bill Wendling <morbo@google.com>
Signed-off-by: Mariia Nikitash <nikitash.mariiaw@gmail.com>
---
This patch was originally part of Bill Wendling's strlcat() removal
series [2], and I am shepherding it individually to the subsystem
maintainers.
No code changes from the original posting [3].
[2] https://lore.kernel.org/all/20260915081910.4142719-1-morbo@google.com/
[3] https://lore.kernel.org/all/20260915081910.4142719-12-morbo@google.com/
.../broadcom/brcm80211/brcmfmac/firmware.c | 21 +++++++------------
1 file changed, 8 insertions(+), 13 deletions(-)
diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/firmware.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/firmware.c
index 22ff326f1924..2f74a952599e 100644
--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/firmware.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/firmware.c
@@ -845,22 +845,17 @@ brcmf_fw_alloc_request(u32 chip, u32 chiprev,
fwreq->n_items = n_fwnames;
for (j = 0; j < n_fwnames; j++) {
- fwreq->items[j].path = fwnames[j].path;
- fwnames[j].path[0] = '\0';
/* check if firmware path is provided by module parameter */
if (brcmf_mp_global.firmware_path[0] != '\0') {
- strscpy(fwnames[j].path, mp_path,
- BRCMF_FW_NAME_LEN);
-
- if (end != '/') {
- strlcat(fwnames[j].path, "/",
- BRCMF_FW_NAME_LEN);
- }
+ snprintf(fwnames[j].path, BRCMF_FW_NAME_LEN, "%s%s%s%s",
+ mp_path, (end == '/') ? "" : "/",
+ mapping_table[i].fw_base,
+ fwnames[j].extension);
+ } else {
+ snprintf(fwnames[j].path, BRCMF_FW_NAME_LEN, "%s%s",
+ mapping_table[i].fw_base,
+ fwnames[j].extension);
}
- strlcat(fwnames[j].path, mapping_table[i].fw_base,
- BRCMF_FW_NAME_LEN);
- strlcat(fwnames[j].path, fwnames[j].extension,
- BRCMF_FW_NAME_LEN);
fwreq->items[j].path = fwnames[j].path;
}
--
2.43.0
reply other threads:[~2026-10-14 0:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261014005553.71803-1-nikitash.mariiaw@gmail.com \
--to=nikitash.mariiaw@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=codemender-patching+linux@google.com \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=morbo@google.com \
/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
all inboxes | Powered by JetHome®