From: Alexey Dobriyan <adobriyan@gmail.com>
To: akpm@linux-foundation.org
Cc: adobriyan@gmail.com, dmantipov@yandex.ru,
andriy.shevchenko@intel.com, linux-kernel@vger.kernel.org
Subject: [PATCH 1/1] Revert "lib: fix _parse_integer_limit() to handle overflow"
Date: Thu, 2 Jul 2026 21:06:38 +0300 [thread overview]
Message-ID: <20260702180638.39196-1-adobriyan@gmail.com> (raw)
This reverts commit 6e30111dbb4075e3c26c230417b32bc4a1c66831 .
1) this patch breaks scanf() which uses _parse_integer_limit()
internally, and is supposed to get overflowed result
(however incorrect it may be)
2) using check_mul_overflow() and check_add_overflow() as written
doesn't add any overflow protection because it is under branch
where such overflow can't happen if radix is kept <=16,
3) kernel-doc comment legitimize the function while exactly
the opposite should be done. Not a fan.
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
---
lib/kstrtox.c | 37 +++++++++++++++----------------------
1 file changed, 15 insertions(+), 22 deletions(-)
diff --git a/lib/kstrtox.c b/lib/kstrtox.c
index edc4eb7c1bca..97be2a39f537 100644
--- a/lib/kstrtox.c
+++ b/lib/kstrtox.c
@@ -39,30 +39,25 @@ const char *_parse_integer_fixup_radix(const char *s, unsigned int *base)
return s;
}
-/**
- * _parse_integer_limit - Convert integer string representation to an integer
- * @s: Integer string representation
- * @base: Radix
- * @p: Where to store result
- * @max_chars: Maximum amount of characters to convert
- *
- * Convert non-negative integer string representation in explicitly given
- * radix to an integer. If overflow occurs, value at @p is set to ULLONG_MAX.
+/*
+ * Convert non-negative integer string representation in explicitly given radix
+ * to an integer. A maximum of max_chars characters will be converted.
*
- * This function is the workhorse of other string conversion functions and it
- * is discouraged to use it explicitly. Consider kstrto*() family instead.
+ * Return number of characters consumed maybe or-ed with overflow bit.
+ * If overflow occurs, result integer (incorrect) is still returned.
*
- * Return: Number of characters consumed, maybe ORed with overflow bit
+ * Don't you dare use this function.
*/
noinline
unsigned int _parse_integer_limit(const char *s, unsigned int base, unsigned long long *p,
size_t max_chars)
{
- unsigned int rv, overflow = 0;
unsigned long long res;
+ unsigned int rv;
res = 0;
- for (rv = 0; rv < max_chars; rv++, s++) {
+ rv = 0;
+ while (max_chars--) {
unsigned int c = *s;
unsigned int lc = _tolower(c);
unsigned int val;
@@ -81,17 +76,15 @@ unsigned int _parse_integer_limit(const char *s, unsigned int base, unsigned lon
* it in the max base we support (16)
*/
if (unlikely(res & (~0ull << 60))) {
- if (check_mul_overflow(res, base, &res) ||
- check_add_overflow(res, val, &res)) {
- res = ULLONG_MAX;
- overflow = KSTRTOX_OVERFLOW;
- }
- } else {
- res = res * base + val;
+ if (res > div_u64(ULLONG_MAX - val, base))
+ rv |= KSTRTOX_OVERFLOW;
}
+ res = res * base + val;
+ rv++;
+ s++;
}
*p = res;
- return rv | overflow;
+ return rv;
}
noinline
--
2.54.0
next reply other threads:[~2026-07-02 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 18:06 Alexey Dobriyan [this message]
2026-07-03 5:55 ` Dmitry Antipov
2026-07-03 6:05 ` Andy Shevchenko
2026-07-03 6:52 ` Dmitry Antipov
2026-07-03 10:21 ` Alexey Dobriyan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260702180638.39196-1-adobriyan@gmail.com \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@intel.com \
--cc=dmantipov@yandex.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox