From: Vincent Mailhol <mailhol@kernel.org>
To: david.laight.linux@gmail.com, Kees Cook <kees@kernel.org>,
linux-hardening@vger.kernel.org, Arnd Bergmann <arnd@kernel.org>,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [PATCH net-next] drivers/net/can/usb/kvaser_usb: User strscpy() to copy device name
Date: Sat, 6 Jun 2026 23:16:47 +0200 [thread overview]
Message-ID: <f8848570-8793-4f5f-a2a4-ab212dcaebcd@kernel.org> (raw)
In-Reply-To: <20260606202633.5018-15-david.laight.linux@gmail.com>
Subject [PATCH net-next] drivers/net/can/usb/kvaser_usb: User strscpy() to copy device name
^^^^
Use?
On 06/06/2026 at 22:26, david.laight.linux@gmail.com wrote:
> From: David Laight <david.laight.linux@gmail.com>
>
> 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.)
Indeed, this is terse. The commit body is empty (all your comments are
below the --- cutter) and the subject line contains a typo.
I don't see why the fact that you are sending many fixes clears you
from writing a proper commit message. And I would expect at least a
small effort to customize the message: only explain the Makefile stuff
for the patches which are touching a Makefile.
> drivers/net/can/usb/kvaser_usb/kvaser_usb_hydra.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/can/usb/kvaser_usb/kvaser_usb_hydra.c b/drivers/net/can/usb/kvaser_usb/kvaser_usb_hydra.c
> index e09d663e362f..2cd58e825e0e 100644
> --- a/drivers/net/can/usb/kvaser_usb/kvaser_usb_hydra.c
> +++ b/drivers/net/can/usb/kvaser_usb/kvaser_usb_hydra.c
> @@ -746,7 +746,7 @@ static int kvaser_usb_hydra_map_channel(struct kvaser_usb *dev, u16 transid,
> if (!cmd)
> return -ENOMEM;
>
> - strcpy(cmd->map_ch_req.name, name);
> + strscpy(cmd->map_ch_req.name, name);
> cmd->header.cmd_no = CMD_MAP_CHANNEL_REQ;
> kvaser_usb_hydra_set_cmd_dest_he
> (cmd, KVASER_USB_HYDRA_HE_ADDRESS_ROUTER);
Yours sincerely,
Vincent Mailhol
next prev parent reply other threads:[~2026-06-06 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 20:26 [PATCH net-next] drivers/net/can/usb/kvaser_usb: User strscpy() to copy device name david.laight.linux
2026-06-06 21:16 ` Vincent Mailhol [this message]
2026-06-07 8: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=f8848570-8793-4f5f-a2a4-ab212dcaebcd@kernel.org \
--to=mailhol@kernel.org \
--cc=arnd@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=kees@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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