From: David Laight <david.laight.linux@gmail.com>
To: yuebingkun <yuebingkun@kylinos.cn>
Cc: Helge Deller <deller@gmx.de>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fbdev: platinumfb: replace strcpy with strscpy
Date: Mon, 17 Aug 2026 15:37:57 +0100 [thread overview]
Message-ID: <20260817153757.4a683d24@pumpkin> (raw)
In-Reply-To: <20260817031816.188833-1-yuebingkun@kylinos.cn>
On Mon, 17 Aug 2026 11:18:16 +0800
yuebingkun <yuebingkun@kylinos.cn> wrote:
> strcpy() is deprecated for use on fixed-size buffers. Replace it with
> strscpy() to avoid potential buffer overflow issues.
There is no point using strscpy() to copy quoted strings into arrays.
Indeed, if the string is too long the kernel build will fail if strcpy()
is used but strscpy() will silently truncate the strings.
So strscpy() is actually worse here.
There are plenty of places where the destination size isn't known.
Which might be worth fixing.
David
>
> Found by checkpatch.pl:
> WARNING: Prefer strscpy over strcpy
>
> Signed-off-by: yuebingkun <yuebingkun@kylinos.cn>
> ---
> drivers/video/fbdev/platinumfb.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/video/fbdev/platinumfb.c b/drivers/video/fbdev/platinumfb.c
> index a08d955d9b43..fa27a3a4f05b 100644
> --- a/drivers/video/fbdev/platinumfb.c
> +++ b/drivers/video/fbdev/platinumfb.c
> @@ -320,7 +320,7 @@ static void platinum_init_info(struct fb_info *info,
> fb_alloc_cmap(&info->cmap, 256, 0);
>
> /* Fill fix common fields */
> - strcpy(info->fix.id, "platinum");
> + strscpy(info->fix.id, "platinum", sizeof(info->fix.id));
> info->fix.mmio_start = pinfo->platinum_regs_phys;
> info->fix.mmio_len = 0x1000;
> info->fix.type = FB_TYPE_PACKED_PIXELS;
prev parent reply other threads:[~2026-08-17 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 3:18 [PATCH] fbdev: platinumfb: replace strcpy with strscpy yuebingkun
2026-08-17 14:37 ` David Laight [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=20260817153757.4a683d24@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuebingkun@kylinos.cn \
/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