Message ID | 20241028191700.GA918263@lichtman.org (mailing list archive) |
---|---|
Headers | show |
Series | Replace the use of simple_strtol/ul functions with kstrto | expand |
On Mon, 28 Oct 2024 19:17:00 +0000, Nir Lichtman wrote: > 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. > > [...] Applied, thanks! [1/3] kdb: Replace the use of simple_strto with safer kstrto in kdb_main commit: fe0c87871fc0b97f6d374b670c81f7c4087eebc5 [2/3] trace: kdb: Replace simple_strtoul with kstrtoul in kdb_ftdump commit: c56642c737fc0bd9bcc3a22a2bf8ed6f5900a660 [3/3] kdb: Remove fallback interpretation of arbitrary numbers as hex commit: 5f4ca702e36893a276fccb0aa55ab36e19dfbb50 Best regards,
On Fri, Nov 08, 2024 at 08:38:35AM +0000, Daniel Thompson wrote: > > On Mon, 28 Oct 2024 19:17:00 +0000, Nir Lichtman wrote: > > 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. > > > > [...] > > Applied, thanks! Thanks! Nir