From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <kees@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/5] lib: fix memparse() to handle overflow
Date: Wed, 4 Feb 2026 16:42:45 +0200 [thread overview]
Message-ID: <aYNa5ZBcA_pJqS7Y@smile.fi.intel.com> (raw)
In-Reply-To: <20260204135717.941256-3-dmantipov@yandex.ru>
On Wed, Feb 04, 2026 at 04:57:14PM +0300, Dmitry Antipov wrote:
> Since '_parse_integer_limit()' (and so 'simple_strtoull()') is now
> capable to handle overflow, adjust 'memparse()' to handle overflow
> (denoted by ULLONG_MAX) returned from 'simple_strtoull()'. Also
> use 'check_shl_overflow()' to catch an overflow possibly caused
> by processing size suffix and denote it with ULLONG_MAX as well.
Do we have already test cases to cover this?
...
> unsigned long long memparse(const char *ptr, char **retptr)
> {
> char *endptr; /* local pointer to end of parsed string */
>
Shouldn't be an empty line in the definition block.
> + unsigned int shl = 0;
> unsigned long long ret = simple_strtoull(ptr, &endptr, 0);
and it would be better to preserve reversed xmas tree order (to some extent).
char *endptr; /* local pointer to end of parsed string */
unsigned long long ret = simple_strtoull(ptr, &endptr, 0);
unsigned int shl = 0;
> + /* Consume valid suffix even in case of overflow. */
> switch (*endptr) {
> case 'E':
> case 'e':
> - ret <<= 10;
> + shl += 10;
> fallthrough;
> case 'P':
> case 'p':
> - ret <<= 10;
> + shl += 10;
> fallthrough;
> case 'T':
> case 't':
> - ret <<= 10;
> + shl += 10;
> fallthrough;
> case 'G':
> case 'g':
> - ret <<= 10;
> + shl += 10;
> fallthrough;
> case 'M':
> case 'm':
> - ret <<= 10;
> + shl += 10;
> fallthrough;
> case 'K':
> case 'k':
> - ret <<= 10;
> + shl += 10;
> endptr++;
> fallthrough;
> default:
> break;
> }
> + /* If no overflow, apply suffix if any. */
> + if (likely(ret != ULLONG_MAX) && shl) {
Do we need to check for shl? Yes, it will be an additional check below,
but do we care?
> + unsigned long long val;
> + ret = (unlikely(check_shl_overflow(ret, shl, &val))
> + ? ULLONG_MAX : val);
Unneeded parentheses, and ? should be on the previous line.
With that said, I prefer to see the regular conditional instead:
ret = check_shl_overflow(...);
if (unlikely(ret))
ret = ...
else
ret = val;
> + }
> +
> if (retptr)
> *retptr = endptr;
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-04 14:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 13:57 [PATCH v5 0/5] lib and lib/cmdline enhancements Dmitry Antipov
2026-02-04 13:57 ` [PATCH v5 1/5] lib: fix _parse_integer_limit() to handle overflow Dmitry Antipov
2026-02-04 14:31 ` Andy Shevchenko
2026-02-05 9:04 ` Dmitry Antipov
2026-02-05 16:03 ` Andy Shevchenko
2026-02-05 22:15 ` David Laight
2026-02-06 7:42 ` Andy Shevchenko
2026-02-06 9:53 ` Dmitry Antipov
2026-02-06 10:11 ` Andy Shevchenko
2026-02-04 13:57 ` [PATCH v5 2/5] lib: fix memparse() " Dmitry Antipov
2026-02-04 14:42 ` Andy Shevchenko [this message]
2026-02-05 9:17 ` Dmitry Antipov
2026-02-05 16:05 ` Andy Shevchenko
2026-02-04 13:57 ` [PATCH v5 3/5] lib: add more string to 64-bit integer conversion overflow tests Dmitry Antipov
2026-02-04 13:57 ` [PATCH v5 4/5] lib/cmdline_kunit: add test case for memparse() Dmitry Antipov
2026-02-04 13:57 ` [PATCH v5 5/5] lib/cmdline: adjust a few comments to fix kernel-doc -Wreturn warnings Dmitry Antipov
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=aYNa5ZBcA_pJqS7Y@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=akpm@linux-foundation.org \
--cc=djwong@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--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