[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241021211221.GA835676@lichtman.org>
Date: Mon, 21 Oct 2024 21:12:21 +0000
From: Nir Lichtman <nir@...htman.org>
To: kgdb-bugreport@...ts.sourceforge.net,
linux-trace-kernel@...r.kernel.org
Cc: yuran.pereira@...mail.com, jason.wessel@...driver.com,
daniel.thompson@...aro.org, dianders@...omium.org,
rostedt@...dmis.org, mhiramat@...nel.org,
linux-kernel@...r.kernel.org,
linux-kernel-mentees@...ts.linuxfoundation.org
Subject: [PATCH v2 0/2] Replace the use of simple_strtol/ul functions with
kstrto
The simple_str* family of functions perform no error checking in
scenarios where the input value overflows the intended output variable.
This results in these function successfully returning even when the
output does not match the input string.
Or as it was mentioned [1], "...simple_strtol(), simple_strtoll(),
simple_strtoul(), and simple_strtoull() functions explicitly ignore
overflows, which may lead to unexpected results in callers."
Hence, the use of those functions is discouraged.
This patch series replaces uses of the simple_strto* series of function
with the safer kstrto* alternatives.
[1] https://www.kernel.org/doc/html/latest/process/deprecated.html#simple-strtol-simple-strtoll-simple-strtoul-simple-strtoull
Yuran Pereira (2):
kdb: Replace the use of simple_strto with safer kstrto in kdb_main
trace: kdb: Replace simple_strtoul with kstrtoul in kdb_ftdump
v2: Nir Lichtman (2): Removed confusing support for hex number inputs with no preceding "0x", and other CR fixes
kernel/debug/kdb/kdb_main.c | 69 +++++++++--------------------------
kernel/trace/trace_kdb.c | 15 +++----- 2 files changed, 23 insertions(+), 61 deletions(-)
Powered by blists - more mailing lists