mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Kees Cook <keescook@chromium.org>
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 21:23:49 +0200	[thread overview]
Message-ID: <af114229f6231ec180266eebce4e62851732a446.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <202306141203.0CAB93DD13@keescook>

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.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2023-06-14 19:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 16:30 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 [this message]
2023-06-14 19:28         ` Kees Cook
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=af114229f6231ec180266eebce4e62851732a446.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=azeemshaikh38@gmail.com \
    --cc=dalias@libc.org \
    --cc=keescook@chromium.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®