From: Kees Cook <keescook@chromium.org>
To: Justin Stitt <justinstitt@google.com>
Cc: Derek Chickles <dchickles@marvell.com>,
Satanand Burla <sburla@marvell.com>,
Felix Manlunas <fmanlunas@marvell.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] net: liquidio: replace deprecated strncpy with strscpy_pad
Date: Thu, 5 Oct 2023 16:16:07 -0700 [thread overview]
Message-ID: <202310051615.4DD6C6C6D@keescook> (raw)
In-Reply-To: <20231005-strncpy-drivers-net-ethernet-cavium-liquidio-lio_main-c-v1-1-663e3f1d8f99@google.com>
On Thu, Oct 05, 2023 at 09:41: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 know `fw_type` must be NUL-terminated based on use here:
> | static bool fw_type_is_auto(void)
> | {
> | return strncmp(fw_type, LIO_FW_NAME_TYPE_AUTO,
> | sizeof(LIO_FW_NAME_TYPE_AUTO)) == 0;
> | }
> ...and here
> | module_param_string(fw_type, fw_type, sizeof(fw_type), 0444);
>
> Let's opt to NUL-pad the destination buffer as well so that we maintain
> the same exact behavior that `strncpy` provided here.
>
> A suitable replacement is `strscpy_pad` due to the fact that it
> guarantees both NUL-termination and NUL-padding on the destination
> buffer.
>
> Link: https://www.kernel.org/doc/html/latest/process/deprecated.html#strncpy-on-nul-terminated-strings [1]
> Link: https://github.com/KSPP/linux/issues/90
> Cc: linux-hardening@vger.kernel.org
> Signed-off-by: Justin Stitt <justinstitt@google.com>
Looks like a safe replacement with strscpy_pad().
Reviewed-by: Kees Cook <keescook@chromium.org>
> ---
> Note: build-tested only.
> ---
> drivers/net/ethernet/cavium/liquidio/lio_main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/cavium/liquidio/lio_main.c b/drivers/net/ethernet/cavium/liquidio/lio_main.c
> index 100daadbea2a..34f02a8ec2ca 100644
> --- a/drivers/net/ethernet/cavium/liquidio/lio_main.c
> +++ b/drivers/net/ethernet/cavium/liquidio/lio_main.c
> @@ -1689,7 +1689,7 @@ static int load_firmware(struct octeon_device *oct)
>
> if (fw_type_is_auto()) {
> tmp_fw_type = LIO_FW_NAME_TYPE_NIC;
> - strncpy(fw_type, tmp_fw_type, sizeof(fw_type));
> + strscpy_pad(fw_type, tmp_fw_type, sizeof(fw_type));
> } else {
> tmp_fw_type = fw_type;
> }
>
> ---
> base-commit: cbf3a2cb156a2c911d8f38d8247814b4c07f49a2
> change-id: 20231005-strncpy-drivers-net-ethernet-cavium-liquidio-lio_main-c-b05f78661635
>
> Best regards,
> --
> Justin Stitt <justinstitt@google.com>
>
>
--
Kees Cook
next prev parent reply other threads:[~2023-10-05 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 21:41 [PATCH] net: liquidio: replace deprecated strncpy with strscpy_pad Justin Stitt
2023-10-05 23:16 ` Kees Cook [this message]
2023-10-10 2:50 ` patchwork-bot+netdevbpf
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=202310051615.4DD6C6C6D@keescook \
--to=keescook@chromium.org \
--cc=davem@davemloft.net \
--cc=dchickles@marvell.com \
--cc=edumazet@google.com \
--cc=fmanlunas@marvell.com \
--cc=justinstitt@google.com \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sburla@marvell.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