From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Justin Stitt <justinstitt@google.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] thermal: intel: int340x_thermal: replace deprecated strncpy with strscpy
Date: Tue, 19 Mar 2024 09:20:26 -0700 [thread overview]
Message-ID: <a2bdac6a8914a76ed122438547f3697611299c0f.camel@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0j=cYbqyfi6y45hnu+Y_tvMGYb9p6d=kpsOA0AsxBoy3g@mail.gmail.com>
On Tue, 2024-03-19 at 12:39 +0100, Rafael J. Wysocki wrote:
> On Mon, Mar 18, 2024 at 11:36 PM Justin Stitt
> <justinstitt@google.com> 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.
> >
> > psvt->limit.string can only be 8 bytes so let's use the appropriate
> > size
> > macro ACPI_LIMIT_STR_MAX_LEN.
> >
> > Neither psvt->limit.string or psvt_user[i].limit.string requires
> > the
> > NUL-padding behavior that strncpy() provides as they have both been
> > filled with NUL-bytes prior to the string operation.
> > > memset(&psvt->limit, 0, sizeof(u64));
> > and
> > > psvt_user = kzalloc(psvt_len, GFP_KERNEL);
> >
> > Let's use `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>
>
> Srinivas, any objections?
No
Reviewed-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
>
> > ---
> > Note: build-tested only.
> >
> > Found with: $ rg "strncpy\("
> > ---
> > drivers/thermal/intel/int340x_thermal/acpi_thermal_rel.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git
> > a/drivers/thermal/intel/int340x_thermal/acpi_thermal_rel.c
> > b/drivers/thermal/intel/int340x_thermal/acpi_thermal_rel.c
> > index dc519a665c18..4b4a4d63e61f 100644
> > --- a/drivers/thermal/intel/int340x_thermal/acpi_thermal_rel.c
> > +++ b/drivers/thermal/intel/int340x_thermal/acpi_thermal_rel.c
> > @@ -309,7 +309,7 @@ static int acpi_parse_psvt(acpi_handle handle,
> > int *psvt_count, struct psvt **ps
> >
> > if (knob->type == ACPI_TYPE_STRING) {
> > memset(&psvt->limit, 0, sizeof(u64));
> > - strncpy(psvt->limit.string, psvt_ptr-
> > >limit.str_ptr, knob->string.length);
> > + strscpy(psvt->limit.string, psvt_ptr-
> > >limit.str_ptr, ACPI_LIMIT_STR_MAX_LEN);
> > } else {
> > psvt->limit.integer = psvt_ptr-
> > >limit.integer;
> > }
> > @@ -468,7 +468,7 @@ static int fill_psvt(char __user *ubuf)
> > psvt_user[i].unlimit_coeff =
> > psvts[i].unlimit_coeff;
> > psvt_user[i].control_knob_type =
> > psvts[i].control_knob_type;
> > if (psvt_user[i].control_knob_type ==
> > ACPI_TYPE_STRING)
> > - strncpy(psvt_user[i].limit.string,
> > psvts[i].limit.string,
> > + strscpy(psvt_user[i].limit.string,
> > psvts[i].limit.string,
> > ACPI_LIMIT_STR_MAX_LEN);
> > else
> > psvt_user[i].limit.integer =
> > psvts[i].limit.integer;
> >
> > ---
> > base-commit: bf3a69c6861ff4dc7892d895c87074af7bc1c400
> > change-id: 20240318-strncpy-drivers-thermal-intel-int340x_thermal-
> > acpi_thermal_rel-c-17070c1e42f3
> >
> > Best regards,
> > --
> > Justin Stitt <justinstitt@google.com>
> >
next prev parent reply other threads:[~2024-03-19 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 22:36 [PATCH] thermal: intel: int340x_thermal: replace deprecated strncpy with strscpy Justin Stitt
2024-03-19 11:39 ` Rafael J. Wysocki
2024-03-19 16:20 ` srinivas pandruvada [this message]
2024-03-27 13:59 ` Rafael J. Wysocki
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=a2bdac6a8914a76ed122438547f3697611299c0f.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=justinstitt@google.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.