All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH v2] video: fbdev: via: refactor strcpy and viafb_name
@ 2026-08-14  6:54 Ajith P V
  2026-08-14  7:01 ` sashiko-bot
  0 siblings, 1 reply; 2+ messages in thread
From: Ajith P V @ 2026-08-14  6:54 UTC (permalink / raw)
  To: FlorianSchandinat, deller; +Cc: linux-fbdev, dri-devel, linux-kernel, Ajith P V

Replace the deprecated and unbounded strcpy() function with the safer
strscpy() alternative when setting up the framebuffer fixed screen
information [1][2].

It aligns this driver with the ongoing kernel-wide security initiative
to eliminate unbounded string copies, hardening the code against future
modifications.

Additionally, convert the file-scope `viafb_name` pointer into a
`static const char[]` array and update its value to "viafb".
This permits the compiler to execute compile-time bounds checking and
aggressively optimize the runtime string copy operation out entirely.

This is a proactive API cleanup and there is no functional performance
or truncation risk.

Link: https://www.kernel.org/doc/html/latest/process/deprecated.html#strcpy [1]
Link: https://github.com/KSPP/linux/issues/88 [2]

Signed-off-by: Ajith P V <ajithpv.linux@gmail.com>
---
v2:
  - Keep variable static but change it to a const array 
    'static const char viafb_name[] = "viafb"' as suggested by Helge Deller 
    to let the compiler leverage compile-time checks.

 drivers/video/fbdev/via/viafbdev.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/video/fbdev/via/viafbdev.c b/drivers/video/fbdev/via/viafbdev.c
index 80f95dac32c8..b3a2e07b61a7 100644
--- a/drivers/video/fbdev/via/viafbdev.c
+++ b/drivers/video/fbdev/via/viafbdev.c
@@ -16,7 +16,7 @@
 #define _MASTER_FILE
 #include "global.h"
 
-static char *viafb_name = "Via";
+static const char viafb_name[] = "viafb";
 static u32 pseudo_pal[17];
 
 /* video mode */
@@ -144,7 +144,7 @@ static void viafb_setup_fixinfo(struct fb_fix_screeninfo *fix,
 	struct viafb_par *viaparinfo)
 {
 	memset(fix, 0, sizeof(struct fb_fix_screeninfo));
-	strcpy(fix->id, viafb_name);
+	strscpy(fix->id, viafb_name, sizeof(fix->id));
 
 	fix->smem_start = viaparinfo->fbmem;
 	fix->smem_len = viaparinfo->fbmem_free;
-- 
2.43.0


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH v2] video: fbdev: via: refactor strcpy and viafb_name
  2026-08-14  6:54 [PATCH v2] video: fbdev: via: refactor strcpy and viafb_name Ajith P V
@ 2026-08-14  7:01 ` sashiko-bot
  0 siblings, 0 replies; 2+ messages in thread
From: sashiko-bot @ 2026-08-14  7:01 UTC (permalink / raw)
  To: Ajith P V; +Cc: dri-devel

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Critical] Changing the driver identification string exposed in the fb_fix_screeninfo structure from "Via" to "viafb" breaks userspace ABI backward compatibility.
--

--- Patch [1]: [PATCH v2] video: fbdev: via: refactor strcpy and viafb_name ---
commit 31193988a75e693bb97d9723171d248ff11a2f17
Author: Ajith P V <ajithpv.linux@gmail.com>

video: fbdev: via: refactor strcpy and viafb_name

This commit replaces unbounded strcpy() calls with strscpy() to harden the
framebuffer screen info initialization. It also converts the viafb_name
pointer into a static const char array and changes its string value.

Link: https://www.kernel.org/doc/html/latest/process/deprecated.html#strcpy [1]
Link: https://github.com/KSPP/linux/issues/88 [2]

> diff --git a/drivers/video/fbdev/via/viafbdev.c b/drivers/video/fbdev/via/viafbdev.c
> index 80f95dac32c8c..b3a2e07b61a7c 100644
> --- a/drivers/video/fbdev/via/viafbdev.c
> +++ b/drivers/video/fbdev/via/viafbdev.c
> @@ -16,7 +16,7 @@
>  #define _MASTER_FILE
>  #include "global.h"
>  
> -static char *viafb_name = "Via";
> +static const char viafb_name[] = "viafb";

[Severity: Critical]
Does changing this string from "Via" to "viafb" cause a userspace ABI
regression?

Userspace tools and display servers, such as Xorg's via driver, often
rely on the exact identification string returned in the id field of
fb_fix_screeninfo by the framebuffer ioctl to detect hardware and apply
specific quirks.

Could the compile-time bounds checking and optimization benefits still be
achieved without modifying the exposed string value, perhaps by defining
it as 'static const char viafb_name[] = "Via";' instead?

>  static u32 pseudo_pal[17];
>  
>  /* video mode */

[ ... ]

> @@ -144,7 +144,7 @@ static void viafb_setup_fixinfo(struct fb_fix_screeninfo *fix,
>  	struct viafb_par *viaparinfo)
>  {
>  	memset(fix, 0, sizeof(struct fb_fix_screeninfo));
> -	strcpy(fix->id, viafb_name);
> +	strscpy(fix->id, viafb_name, sizeof(fix->id));
>  
>  	fix->smem_start = viaparinfo->fbmem;
>  	fix->smem_len = viaparinfo->fbmem_free;

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260814065433.269375-1-ajithpv.linux@gmail.com?part=1

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-08-14  7:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-08-14  6:54 [PATCH v2] video: fbdev: via: refactor strcpy and viafb_name Ajith P V
2026-08-14  7:01 ` sashiko-bot

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.