From: Kees Cook <keescook@chromium.org>
To: Justin Stitt <justinstitt@google.com>
Cc: Kalle Valo <kvalo@kernel.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] wifi: wlcore: main: replace deprecated strncpy with strscpy
Date: Wed, 18 Oct 2023 22:31:23 -0700 [thread overview]
Message-ID: <202310182231.052A44F@keescook> (raw)
In-Reply-To: <20231018-strncpy-drivers-net-wireless-ti-wlcore-main-c-v1-1-1b1055f482a1@google.com>
On Wed, Oct 18, 2023 at 09:50:01PM +0000, Justin Stitt wrote:
> strncpy() is deprecated for use on NUL-terminated destination strings
> [1] and as such we should prefer more robust and less ambiguous string
> interfaces.
>
> We expect fw_version strings to be NUL-terminated based on other similar
> assignments:
>
> wireless/broadcom/brcm80211/brcmsmac/main.c
> 7867: snprintf(wlc->wiphy->fw_version,
> 7868: sizeof(wlc->wiphy->fw_version), "%u.%u", rev, patch);
>
> wireless/broadcom/b43legacy/main.c
> 1765: snprintf(wiphy->fw_version, sizeof(wiphy->fw_version), "%u.%u",
>
> wireless/broadcom/b43/main.c
> 2730: snprintf(wiphy->fw_version, sizeof(wiphy->fw_version), "%u.%u",
>
> wireless/intel/iwlwifi/dvm/main.c
> 1465: snprintf(priv->hw->wiphy->fw_version,
> 1466: sizeof(priv->hw->wiphy->fw_version),
>
> wireless/intel/ipw2x00/ipw2100.c
> 5905: snprintf(info->fw_version, sizeof(info->fw_version), "%s:%d:%s",
>
> Based on this, NUL-padding is not required.
>
> A suitable replacement is `strscpy` [2] due to the fact that it
> guarantees NUL-termination on the destination buffer without
> unnecessarily NUL-padding.
>
> Link: https://www.kernel.org/doc/html/latest/process/deprecated.html#strncpy-on-nul-terminated-strings [1]
> Link: https://manpages.debian.org/testing/linux-manual-4.8/strscpy.9.en.html [2]
> Link: https://github.com/KSPP/linux/issues/90
> Cc: linux-hardening@vger.kernel.org
> Signed-off-by: Justin Stitt <justinstitt@google.com>
More clear replacements.
Reviewed-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
next prev parent reply other threads:[~2023-10-19 5:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 21:50 [PATCH] wifi: wlcore: main: replace deprecated strncpy with strscpy Justin Stitt
2023-10-19 5:31 ` Kees Cook [this message]
2023-10-23 17:30 ` Kalle Valo
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=202310182231.052A44F@keescook \
--to=keescook@chromium.org \
--cc=justinstitt@google.com \
--cc=kvalo@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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).