[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240826045253.3503-1-shenlichuan@vivo.com>
Date: Mon, 26 Aug 2024 12:52:53 +0800
From: Shen Lichuan <shenlichuan@...o.com>
To: mitr@...ny.cz,
dmitry.torokhov@...il.com
Cc: linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org,
Shen Lichuan <shenlichuan@...o.com>
Subject: [PATCH v1] Input: wistron_btns - use kmemdup_array instead of kmemdup for multiple allocation
Let the kmemdup_array() take care about multiplication
and possible overflows.
Using kmemdup_array() is more appropriate and makes the code
easier to audit.
Signed-off-by: Shen Lichuan <shenlichuan@...o.com>
---
drivers/input/misc/wistron_btns.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/input/misc/wistron_btns.c b/drivers/input/misc/wistron_btns.c
index 5c4956678cd0..907b1a4e6633 100644
--- a/drivers/input/misc/wistron_btns.c
+++ b/drivers/input/misc/wistron_btns.c
@@ -990,8 +990,8 @@ static int __init copy_keymap(void)
for (key = keymap; key->type != KE_END; key++)
length++;
- new_keymap = kmemdup(keymap, length * sizeof(struct key_entry),
- GFP_KERNEL);
+ new_keymap = kmemdup_array(keymap, length, sizeof(struct key_entry),
+ GFP_KERNEL);
if (!new_keymap)
return -ENOMEM;
--
2.17.1
Powered by blists - more mailing lists