kdb: Remove fallback interpretation of arbitrary numbers as hex

Remove logic that enables a fallback of interpreting numbers supplied in KDB CLI
to be interpreted as hex without explicit "0x" prefix as this can be confusing
for the end users.

Suggested-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Signed-off-by: Nir Lichtman <nir@lichtman.org>
Link: https://lore.kernel.org/r/20241028192228.GC918454@lichtman.org
Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
This commit is contained in:
Nir Lichtman 2024-10-28 19:22:28 +00:00 committed by Daniel Thompson
parent 0c10cc2435
commit 9131d6a7a7

View File

@ -402,23 +402,15 @@ static void kdb_printenv(void)
*/
int kdbgetularg(const char *arg, unsigned long *value)
{
/*
* If the first fails, also try base 16, for us
* folks too lazy to type the leading 0x...
*/
if (kstrtoul(arg, 0, value)) {
if (kstrtoul(arg, 16, value))
return KDB_BADINT;
}
if (kstrtoul(arg, 0, value))
return KDB_BADINT;
return 0;
}
int kdbgetu64arg(const char *arg, u64 *value)
{
if (kstrtou64(arg, 0, value)) {
if (kstrtou64(arg, 16, value))
return KDB_BADINT;
}
if (kstrtou64(arg, 0, value))
return KDB_BADINT;
return 0;
}