From: Joe Perches <joe@perches.com>
To: Borislav Petkov <bp@alien8.de>, Len Baker <len.baker@gmx.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Tony Luck <tony.luck@intel.com>,
James Morse <james.morse@arm.com>,
Robert Richter <rric@kernel.org>,
David Laight <David.Laight@aculab.com>,
Kees Cook <keescook@chromium.org>,
linux-hardening@vger.kernel.org, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] EDAC/mc: Prefer strscpy over strcpy
Date: Tue, 24 Aug 2021 12:05:52 -0700 [thread overview]
Message-ID: <6dd7d45d8dccacb6d37ad5f6f137413b229d8565.camel@perches.com> (raw)
In-Reply-To: <YSU5wp/ZpsXuDgmu@zn.tnic>
On Tue, 2021-08-24 at 20:26 +0200, Borislav Petkov wrote:
> On Tue, Aug 24, 2021 at 12:28:07PM +0200, Len Baker wrote:
> > This is a task of the KSPP [1] and the main reason is to clean up the
> > proliferation of str*cpy functions in the kernel.
>
> That I understood - you prominently explain where the patches stem from.
>
> What I can't parse is that formulation "previous step". What previous
> step do you mean?
>
> > Yes, you are right. The same discussion happened in the v3 review [2] and
> > I agree with the reasons that Robert Richter exposed. Using the strlen()
> > implementation it is not necessary to check the return code of strcpy and
> > we can assume a silent truncation.
> >
> > [2] https://lore.kernel.org/linux-hardening/YRN+8u59lJ6MWsOL@rric.localdomain/
>
> Ok, looking at the asm, gcc is actually smart enough not to call
> strlen() twice on the same buffer.
>
> But then there's this in the strscpy() kernel-doc comment:
>
> "The destination buffer is always NUL terminated, unless it's
> zero-sized."
>
> so looking at the code, we're merrily decrementing len but nothing's
> checking whether len can become 0. Because if it does, strscpy() will
> do:
>
> if (count == 0 || WARN_ON_ONCE(count > INT_MAX))
> return -E2BIG;
>
> so if p ends up pointing to something which is *not* '\0', strlen() will
> go off into the weeds.
>
> So I don't care if it doesn't look just as nice - it better be correct
> in all cases first.
It's all somehat unnecessary as it seems it's guaranteed not to overflow.
$ git grep -n -w OTHER_LABEL next-20210820
next-20210820:drivers/edac/edac_mc.c:1118: strcpy(p, OTHER_LABEL);
next-20210820:drivers/edac/edac_mc.c:1119: p += strlen(OTHER_LABEL);
next-20210820:include/linux/edac.h:57:#define OTHER_LABEL " or "
next-20210820:include/linux/edac.h:470: char label[(EDAC_MC_LABEL_LEN + 1 + sizeof(OTHER_LABEL)) * EDAC_MAX_LABELS];
Also the array size of char label is too large.
First by 1 * EDAC_MAX_LABELS as sizeof(OTHER_LABEL) is 5 not 4 and
second there can only be EDAC_MAX_LABELS - 1 uses of OTHER_LABEL.
And I would remove the define for OTHER_LABEL and use " or " directly.
Lastly, this could be easier to understand using stpcpy and/or scnprintf.
next prev parent reply other threads:[~2021-08-24 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 7:55 [PATCH v4] EDAC/mc: Prefer strscpy over strcpy Len Baker
2021-08-23 17:30 ` Borislav Petkov
2021-08-24 10:28 ` Len Baker
2021-08-24 18:26 ` Borislav Petkov
2021-08-24 19:05 ` Joe Perches [this message]
2021-08-25 8:48 ` David Laight
2021-08-27 17:36 ` Len Baker
2021-08-27 17:54 ` Borislav Petkov
2021-08-27 19:08 ` Joe Perches
2021-08-29 16:14 ` Len Baker
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=6dd7d45d8dccacb6d37ad5f6f137413b229d8565.camel@perches.com \
--to=joe@perches.com \
--cc=David.Laight@aculab.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=keescook@chromium.org \
--cc=len.baker@gmx.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rric@kernel.org \
--cc=tony.luck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).