From: Lee Jones <lee@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: Justin Stitt <justinstitt@google.com>,
Pavel Machek <pavel@ucw.cz>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] leds: lp3952: replace deprecated strncpy with strscpy
Date: Thu, 28 Sep 2023 14:41:59 +0100 [thread overview]
Message-ID: <20230928134159.GJ9999@google.com> (raw)
In-Reply-To: <202309232039.979F3B4@keescook>
On Sat, 23 Sep 2023, Kees Cook wrote:
> On Fri, Sep 22, 2023 at 03:27:17PM +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 `dest` to be NUL-terminated due to its use with dev_err.
> >
> > lp3952_get_label()'s dest argument is priv->leds[i].name:
> > | acpi_ret = lp3952_get_label(&priv->client->dev, led_name_hdl[i],
> > | priv->leds[i].name);
> > ... which is then assigned to:
> > | priv->leds[i].cdev.name = priv->leds[i].name;
> > ... which is used with a format string
> > | dev_err(&priv->client->dev,
> > | "couldn't register LED %s\n",
> > | priv->leds[i].cdev.name);
> >
> > There is no indication that NUL-padding is required but if it is let's
> > opt for strscpy_pad.
> >
> > Considering the above, 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>
> > ---
> > Note: build-tested only.
> > ---
> > drivers/leds/leds-lp3952.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/leds/leds-lp3952.c b/drivers/leds/leds-lp3952.c
> > index 3bd55652a706..62ade3f05a87 100644
> > --- a/drivers/leds/leds-lp3952.c
> > +++ b/drivers/leds/leds-lp3952.c
> > @@ -101,7 +101,7 @@ static int lp3952_get_label(struct device *dev, const char *label, char *dest)
> > if (ret)
> > return ret;
> >
> > - strncpy(dest, str, LP3952_LABEL_MAX_LEN);
> > + strscpy(dest, str, LP3952_LABEL_MAX_LEN);
>
> Given my desire to use sizeof(dest) for these things, I wonder if it'd
> be nicer to pass more context here for the compiler as the only user of
> this function is the immediately next function. Instead of passing in
> "char *dest", it could pass "struct lp3952_led_array *priv", and
> suddenly sizeof() would be possible.
>
> But, since it's technically correct as-is:
>
> struct lp3952_ctrl_hdl {
> struct led_classdev cdev;
> char name[LP3952_LABEL_MAX_LEN];
>
> There's no pressing need to actually do the priv refactor. It's just a
> comment on the coding style of the original code. :)
>
> Reviewed-by: Kees Cook <keescook@chromium.org>
I've applied this as-is, but please consider Kees' proposal.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-09-28 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 15:27 [PATCH] leds: lp3952: replace deprecated strncpy with strscpy Justin Stitt
2023-09-24 3:43 ` Kees Cook
2023-09-28 13:41 ` Lee Jones [this message]
2023-09-28 13:41 ` (subset) " Lee Jones
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=20230928134159.GJ9999@google.com \
--to=lee@kernel.org \
--cc=justinstitt@google.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.