[PATCH v2] KDB: Fix incorrect treatment of numbers in the CLI

From: Nir Lichtman
Date: Sat Oct 19 2024 - 16:42:20 EST


Problem: In many cases, KDB treats invalid commands as numbers and
instead of printing a usage error, goes ahead and just prints the number
in hex

Example: This can be demonstrated when typing for example "aaazzz", this
confuses KDB into thinking this is the hexadecimal 0xAAA

Solution: Transition to using kstrtoul instead of simple_strtoul.
This function is more strict with what it treats as a number
and thus solves the issue.
(also better practice as stated in the definition of simple_strtoul).

v2: Removed redundant if condition I put in v1

Signed-off-by: Nir Lichtman <nir@xxxxxxxxxxxx>
---
kernel/debug/kdb/kdb_main.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/kernel/debug/kdb/kdb_main.c b/kernel/debug/kdb/kdb_main.c
index f5f7d7fb5936..4cbd5cd26821 100644
--- a/kernel/debug/kdb/kdb_main.c
+++ b/kernel/debug/kdb/kdb_main.c
@@ -402,18 +402,15 @@ static void kdb_printenv(void)
*/
int kdbgetularg(const char *arg, unsigned long *value)
{
- char *endp;
unsigned long val;

- val = simple_strtoul(arg, &endp, 0);

- if (endp == arg) {
+ if (kstrtoul(arg, 0, &val) != 0) {
/*
* Also try base 16, for us folks too lazy to type the
* leading 0x...
*/
- val = simple_strtoul(arg, &endp, 16);
- if (endp == arg)
+ if (kstrtoul(arg, 16, &val) != 0)
return KDB_BADINT;
}

--
2.39.2