From: Kees Cook <keescook@chromium.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: ysato@users.sourceforge.jp, azeemshaikh38@gmail.com,
dalias@libc.org, linux-kernel@vger.kernel.org,
rdunlap@infradead.org, linux-sh@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] sh: Replace all non-returning strlcpy with strscpy
Date: Wed, 14 Jun 2023 12:28:18 -0700 [thread overview]
Message-ID: <202306141227.D4B2F1F6@keescook> (raw)
In-Reply-To: <af114229f6231ec180266eebce4e62851732a446.camel@physik.fu-berlin.de>
On Wed, Jun 14, 2023 at 09:23:49PM +0200, John Paul Adrian Glaubitz wrote:
> On Wed, 2023-06-14 at 12:03 -0700, Kees Cook wrote:
> > On Wed, Jun 14, 2023 at 08:49:13PM +0200, John Paul Adrian Glaubitz wrote:
> > > Hi Kees!
> > >
> > > On Wed, 2023-06-14 at 11:44 -0700, Kees Cook wrote:
> > > > On Tue, 30 May 2023 16:30:41 +0000, Azeem Shaikh wrote:
> > > > > strlcpy() reads the entire source buffer first.
> > > > > This read may exceed the destination size limit.
> > > > > This is both inefficient and can lead to linear read
> > > > > overflows if a source string is not NUL-terminated [1].
> > > > > In an effort to remove strlcpy() completely [2], replace
> > > > > strlcpy() here with strscpy().
> > > > > No return values were used, so direct replacement is safe.
> > > > >
> > > > > [...]
> > > >
> > > > Build tested with sh4 GCC 13.1 from:
> > > > https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/13.1.0/
> > > >
> > > > with defconfig and:
> > > > CONFIG_CPU_SUBTYPE_SH7343=y
> > > > CONFIG_SH_DMA=y
> > > > CONFIG_SH_DMA_API=y
> > > >
> > > > Applied to for-next/hardening, thanks!
> > > >
> > > > [1/1] sh: Replace all non-returning strlcpy with strscpy
> > > > https://git.kernel.org/kees/c/ca64da3052be
> > > >
> > >
> > > Apologies, this fell off my table. I should have acked and tested this being the
> > > SuperH maintainer. If you can still update the patch in your tree, I can both
> > > test and ack this patch.
> >
> > Absolutely! Thanks for double-checking. :)
>
> I have tested the patch on my SH-7785LCR board on top of Linus' tree and
> also acked it.
Awesome. :) I have updated the tags and will push out my tree shortly.
Thanks!
-Kees
--
Kees Cook
next prev parent reply other threads:[~2023-06-14 19:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 16:30 [PATCH] sh: Replace all non-returning strlcpy with strscpy Azeem Shaikh
2023-05-30 23:21 ` Kees Cook
2023-06-14 18:44 ` Kees Cook
2023-06-14 18:49 ` John Paul Adrian Glaubitz
2023-06-14 19:03 ` Kees Cook
2023-06-14 19:23 ` John Paul Adrian Glaubitz
2023-06-14 19:28 ` Kees Cook [this message]
2023-06-14 19:22 ` John Paul Adrian Glaubitz
2023-06-14 19:22 ` John Paul Adrian Glaubitz
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=202306141227.D4B2F1F6@keescook \
--to=keescook@chromium.org \
--cc=azeemshaikh38@gmail.com \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=ysato@users.sourceforge.jp \
/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.