From: Kees Cook <keescook@chromium.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Andy Shevchenko <andy@kernel.org>,
Richard Weinberger <richard@nod.at>,
linux-um@lists.infradead.org,
Justin Stitt <justinstitt@google.com>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Jason Wang <jasowang@redhat.com>,
kernel test robot <lkp@intel.com>,
Nathan Chancellor <nathan@kernel.org>,
Azeem Shaikh <azeemshaikh38@gmail.com>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Removing more str APIs (was Re: [PATCH v3 4/4] um: Convert strscpy() usage to 2-argument style)
Date: Wed, 7 Feb 2024 02:42:42 -0800 [thread overview]
Message-ID: <202402070234.79D2985585@keescook> (raw)
In-Reply-To: <CAHp75Vf3c0Q7tV8ih5fRL6Bsjr6dhspFe+mxV7xUN=vZ1JdTKQ@mail.gmail.com>
On Tue, Feb 06, 2024 at 05:02:16PM +0200, Andy Shevchenko wrote:
> On Tue, Feb 6, 2024 at 4:22 PM Kees Cook <keescook@chromium.org> wrote:
> >
> > The ARCH=um build has its own idea about strscpy()'s definition. Adjust
> > the callers to remove the redundant sizeof() arguments ahead of treewide
> > changes, since it needs a manual adjustment for the newly named
> > sized_strscpy() export.
>
> ...
>
> > - strscpy(dir, home, sizeof(dir));
> > + strscpy(dir, home);
> > uml_dir++;
> > }
> > strlcat(dir, uml_dir, sizeof(dir));
>
> An (unrelated) side note: are we going to get rid of strlcat() as well
> (after strlcpy() is gone)?
I think it would be worthwhile to remove it, yes. Switching to seq_buf
in many cases seemed to be the clear solution, which is what triggered
my trying to improve the allocation ergonomics for seq_buf recently:
https://lore.kernel.org/linux-hardening/20231027155634.make.260-kees@kernel.org/
Its not in super common usage, so I think we can start chipping away at
it:
$ git grep '\bstrlcat(' | wc -l
480
It's more risky cases (using the return value) is relatively rare,
though, so I hadn't been prioritizing its removal:
$ git grep ' = strlcat(\b' | wc -l
13
(And almost all of it is in security/selinux/ima.c)
As a comparison, strncpy has even fewer currently, with Justin making a
dent on it recently:
$ git grep '\bstrncpy(' | wc -l
311
>
> ...
>
> > if (*umid == '\0') {
> > - strscpy(tmp, uml_dir, sizeof(tmp));
> > + strscpy(tmp, uml_dir);
> > strlcat(tmp, "XXXXXX", sizeof(tmp));
>
> This code is interesting... (Esp. taking into account making a
> temporary folder out of this...)
I have tried to avoid reading UML code too closely. ;)
--
Kees Cook
prev parent reply other threads:[~2024-02-07 10:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 14:22 [PATCH v3 0/4] string: Allow 2-argument strscpy() Kees Cook
2024-02-06 14:22 ` [PATCH v3 1/4] string: Redefine strscpy_pad() as a macro Kees Cook
2024-02-07 0:32 ` Justin Stitt
2024-02-06 14:22 ` [PATCH v3 2/4] string: Allow 2-argument strscpy() Kees Cook
2024-02-06 14:22 ` [PATCH v3 3/4] string: Allow 2-argument strscpy_pad() Kees Cook
2024-02-07 0:51 ` Justin Stitt
2024-02-07 9:18 ` Kees Cook
2024-02-10 12:34 ` David Laight
2024-02-06 14:22 ` [PATCH v3 4/4] um: Convert strscpy() usage to 2-argument style Kees Cook
2024-02-06 15:02 ` Andy Shevchenko
2024-02-07 10:42 ` Kees Cook [this message]
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=202402070234.79D2985585@keescook \
--to=keescook@chromium.org \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=azeemshaikh38@gmail.com \
--cc=jasowang@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=justinstitt@google.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=lkp@intel.com \
--cc=nathan@kernel.org \
--cc=richard@nod.at \
--cc=willemdebruijn.kernel@gmail.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