From: Thorsten Blum <thorsten.blum@linux.dev>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ard Biesheuvel <ardb@kernel.org>,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Arnd Bergmann <arnd@arndb.de>, Jiri Bohac <jbohac@suse.cz>,
Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
linux-hardening@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/setup: replace strlcat() with snprintf() in setup_arch()
Date: Fri, 5 Jun 2026 17:42:48 +0200 [thread overview]
Message-ID: <aiLueGQiArrWeUJv@linux.dev> (raw)
In-Reply-To: <aiJTZ9P7_bvRWlqw@ashevche-desk.local>
On Fri, Jun 05, 2026 at 07:41:11AM +0300, Andy Shevchenko wrote:
> On Thu, Jun 04, 2026 at 03:17:53PM +0200, Thorsten Blum wrote:
> > In preparation to remove strlcat() from the kernel [1], replace two
> > strlcat() calls with one snprintf() call in setup_arch().
> >
> > Also drop the explicit size argument of strscpy() to further simplify
> > the code since strscpy() can determine the size automatically when the
> > destination buffer has a fixed length.
>
> > [1] https://github.com/KSPP/linux/issues/370
>
> Make it Link tag?
>
> ...
>
> > strscpy(boot_command_line, builtin_cmdline, COMMAND_LINE_SIZE);
>
> This also has third argument fixed. Don't you want to change that?
That doesn't work because boot_command_line, at least the declaration in
linux/init.h, doesn't have a fixed size.
> > #else
> > if (builtin_cmdline[0]) {
> > + size_t len = strnlen(builtin_cmdline, COMMAND_LINE_SIZE);
> > +
> > /* append boot loader cmdline to builtin */
> > - strlcat(builtin_cmdline, " ", COMMAND_LINE_SIZE);
> > - strlcat(builtin_cmdline, boot_command_line, COMMAND_LINE_SIZE);
> > + snprintf(builtin_cmdline + len, COMMAND_LINE_SIZE - len, " %s",
> > + boot_command_line);
>
> Hmm... Wouldn't GCC complain on this? (Build with `make W=1`.)
No warnings with W=1. Why would GCC warn here?
> > strscpy(boot_command_line, builtin_cmdline, COMMAND_LINE_SIZE);
>
> And this has also third argument.
Same reason as above.
Thanks,
Thorsten
next prev parent reply other threads:[~2026-06-05 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 13:17 [PATCH] x86/setup: replace strlcat() with snprintf() in setup_arch() Thorsten Blum
2026-06-05 4:41 ` Andy Shevchenko
2026-06-05 15:42 ` Thorsten Blum [this message]
2026-06-05 15:55 ` Andy Shevchenko
2026-06-05 18:05 ` Thorsten Blum
2026-06-05 18:28 ` Andy Shevchenko
2026-06-06 10:12 ` David Laight
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=aiLueGQiArrWeUJv@linux.dev \
--to=thorsten.blum@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=hpa@zytor.com \
--cc=jbohac@suse.cz \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=rppt@kernel.org \
--cc=tglx@kernel.org \
--cc=tzimmermann@suse.de \
--cc=x86@kernel.org \
/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