staging: vme_user: prefer strscpy over strcpy

Using strcpy has potential for buffer overflows. It should be replaced
with strscpy where possible. In this case the return value of strcpy is
not used, so we can safely replace it with strscpy.

Signed-off-by: Michael Straube <straube.linux@gmail.com>
Link: https://lore.kernel.org/r/20231023090001.7273-1-straube.linux@gmail.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

diff --git a/drivers/staging/vme_user/vme_tsi148.c b/drivers/staging/vme_user/vme_tsi148.c
index d549c22da534d47c75cee7c2a9df90b3ae44d00b..2ec9c2904404141597ddd9a2849d0124fc5ae902 100644 (file)
--- a/drivers/staging/vme_user/vme_tsi148.c
+++ b/drivers/staging/vme_user/vme_tsi148.c
@@ -2310,7 +2310,7 @@ static int tsi148_probe(struct pci_dev *pdev, const struct pci_device_id *id)
        mutex_init(&tsi148_device->vme_rmw);
 
        tsi148_bridge->parent = &pdev->dev;
-       strcpy(tsi148_bridge->name, driver_name);
+       strscpy(tsi148_bridge->name, driver_name, VMENAMSIZ);
 
        /* Setup IRQ */
        retval = tsi148_irq_init(tsi148_bridge);