From: Jakub Kicinski <kuba@kernel.org>
To: david.laight.linux@gmail.com
Cc: Kees Cook <kees@kernel.org>,
linux-hardening@vger.kernel.org, Arnd Bergmann <arnd@kernel.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jay Vosburgh <jv@jvosburgh.net>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next] drivers/net/bonding: User strscpy() to copy device name
Date: Tue, 9 Jun 2026 17:58:41 -0700 [thread overview]
Message-ID: <20260609175841.3ce88cf0@kernel.org> (raw)
In-Reply-To: <20260606202633.5018-14-david.laight.linux@gmail.com>
On Sat, 6 Jun 2026 21:26:08 +0100 david.laight.linux@gmail.com wrote:
> From: David Laight <david.laight.linux@gmail.com>
Commit message is required. Please explain why you think this patch is
needed. AFAICT it copies data between two well formed IFNAMSIZ strings.
> 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.)
>
> drivers/net/bonding/bond_options.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/bonding/bond_options.c b/drivers/net/bonding/bond_options.c
> index 7380cc4ee75a..c57b7d6af043 100644
> --- a/drivers/net/bonding/bond_options.c
> +++ b/drivers/net/bonding/bond_options.c
> @@ -1525,7 +1525,7 @@ static int bond_option_primary_set(struct bonding *bond,
> if (strncmp(slave->dev->name, primary, IFNAMSIZ) == 0) {
> slave_dbg(bond->dev, slave->dev, "Setting as primary slave\n");
> rcu_assign_pointer(bond->primary_slave, slave);
> - strcpy(bond->params.primary, slave->dev->name);
> + strscpy(bond->params.primary, slave->dev->name);
> bond->force_primary = true;
> bond_select_active_slave(bond);
> goto out;
--
pw-bot: cr
next prev parent reply other threads:[~2026-06-10 0:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 20:26 [PATCH net-next] drivers/net/bonding: User strscpy() to copy device name david.laight.linux
2026-06-10 0:58 ` Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-06 20:26 david.laight.linux
2026-06-08 20:23 ` Jakub Kicinski
2026-06-08 21:07 ` David Laight
2026-06-08 21:18 ` Jakub Kicinski
2026-06-08 21:40 ` 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=20260609175841.3ce88cf0@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=arnd@kernel.org \
--cc=davem@davemloft.net \
--cc=david.laight.linux@gmail.com \
--cc=edumazet@google.com \
--cc=jv@jvosburgh.net \
--cc=kees@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox