From: Kees Cook <kees@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: david.laight.linux@gmail.com, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Arnd Bergmann <arnd@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Jiri Pirko <jiri@resnulli.us>
Subject: Re: [PATCH net-next] net/devlink: Use strscpy() to copy strings into arrays
Date: Wed, 10 Jun 2026 13:58:51 -0700 [thread overview]
Message-ID: <202606101355.6353D5C1@keescook> (raw)
In-Reply-To: <c6eb816c-3f2d-4705-82ea-8c2c0ad70ded@redhat.com>
On Tue, Jun 09, 2026 at 03:39:35PM +0200, Paolo Abeni wrote:
> On 6/8/26 11:54 AM, david.laight.linux@gmail.com wrote:
> > From: David Laight <david.laight.linux@gmail.com>
> >
> > Replacing strcpy() with strscpy() ensures that overflow of the target
> > buffer cannot happen.
> >
> > Signed-off-by: David Laight <david.laight.linux@gmail.com>
> > ---
> > This is one of a group of patches that remove potentially unbounded
> > strcpy() calls.
> >
> > They are mostly replaced by strscpy() or, when strlen() has just been
> > called, with memcpy() (usually including the '\0').
> >
> > Calls with copy string literals into arrays are left unchanged.
> > They are safe and easily detected as such.
> >
> > The changes were made by getting the compiler to detect the calls and
> > then fixing the code by hand.
> >
> > Note that all the changes are only compile tested.
> >
> > Some Makefiles were changed to allow files to contain strcpy().
> > As well as 'difficult to fix' files, this included 'show' functions
> > as they really need to use sysfs_emit() or seq_printf().
> >
> > All the patches are being sent individually to avoid very long cc lists.
> > Apologies for the terse commit messages and likely unexpected tags.
> > (There are about 100 patches in total.)
> >
> > net/devlink/port.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/net/devlink/port.c b/net/devlink/port.c
> > index 485029d43428..108926d3f899 100644
> > --- a/net/devlink/port.c
> > +++ b/net/devlink/port.c
> > @@ -1222,7 +1222,7 @@ static void __devlink_port_type_set(struct devlink_port *devlink_port,
> > devlink_port->type_eth.ifindex = netdev->ifindex;
> > BUILD_BUG_ON(sizeof(devlink_port->type_eth.ifname) !=
> > sizeof(netdev->name));
> > - strcpy(devlink_port->type_eth.ifname, netdev->name);
> > + strscpy(devlink_port->type_eth.ifname, netdev->name);
>
> Given the above BUILD_BUG, I don't see how this change can help?!?
>
> Generally speaking, I suggest restricting this kind of tool-assisted
> changes to real problems (if any).
How did this patch get generated? This isn't an "unbounded" case: both
devlink_port->type_eth.ifname and netdev->name have known sizes. I think
a way to focus these kinds of refactors would be to replace strcpy()
with a macro wrapper that fails a build when the sizes aren't known, but
then otherwise calls strscpy instead. With that in place, you can find
all the actually unbounded cases and work through each of them, and once
they have all been purged from the kernel, that strcpy macro can land,
which will keep new unbounded instances from showing up.
--
Kees Cook
next prev parent reply other threads:[~2026-06-10 20:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 9:54 [PATCH net-next] net/devlink: Use strscpy() to copy strings into arrays david.laight.linux
2026-06-09 13:39 ` Paolo Abeni
2026-06-09 15:13 ` David Laight
2026-06-10 21:14 ` Kees Cook
2026-06-10 20:58 ` Kees Cook [this message]
2026-06-10 21:52 ` David Laight
-- strict thread matches above, loose matches on Subject: below --
2026-06-08 9:54 david.laight.linux
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=202606101355.6353D5C1@keescook \
--to=kees@kernel.org \
--cc=arnd@kernel.org \
--cc=davem@davemloft.net \
--cc=david.laight.linux@gmail.com \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.