From: Kalle Valo <kvalo@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: Justin Stitt <justinstitt@google.com>,
Gregory Greenman <gregory.greenman@intel.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2] wifi: iwlwifi: fw: replace deprecated strncpy with strscpy_pad
Date: Fri, 01 Dec 2023 14:27:15 +0200 [thread overview]
Message-ID: <874jh2rtuk.fsf@kernel.org> (raw)
In-Reply-To: <202311301354.0DAC97C@keescook> (Kees Cook's message of "Thu, 30 Nov 2023 13:55:04 -0800")
Kees Cook <keescook@chromium.org> writes:
> On Thu, Oct 19, 2023 at 05:44:59PM +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.
>>
>> Based on the deliberate `sizeof(dest) ... - 1` pattern we can see that
>> both dump_info->dev_human_readable and dump_info->bus_human_readable are
>> intended to be NUL-terminated.
>>
>> Moreover, since this seems to cross the file boundary let's NUL-pad to
>> ensure no behavior change.
>>
>> strscpy_pad() covers both the NUL-termination and NUL-padding, let's use
>> it.
>>
>> 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>
>
> Thread ping. Can the wireless folks please pick this up?
Yeah, I'll take this directly to wireless-next.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-12-01 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 17:44 [PATCH v2] wifi: iwlwifi: fw: replace deprecated strncpy with strscpy_pad Justin Stitt
2023-10-20 0:16 ` Kees Cook
2023-11-30 21:55 ` Kees Cook
2023-12-01 12:27 ` Kalle Valo [this message]
2023-12-01 12:39 ` 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=874jh2rtuk.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=gregory.greenman@intel.com \
--cc=justinstitt@google.com \
--cc=keescook@chromium.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