From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: <pmladek@suse.com>, <rostedt@goodmis.org>,
<sergey.senozhatsky@gmail.com>, <linux@rasmusvillemoes.dk>,
<shuah@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>,
<patches@opensource.cirrus.com>
Subject: Re: [PATCH v7 2/4] lib: vsprintf: Fix handling of number field widths in vsscanf
Date: Mon, 29 Mar 2021 17:27:32 +0100 [thread overview]
Message-ID: <9741fc05-52e2-378a-a7ce-9a3fff7c1340@opensource.cirrus.com> (raw)
In-Reply-To: <YGHX73vumna0AfwD@smile.fi.intel.com>
On 29/03/2021 14:36, Andy Shevchenko wrote:
> On Mon, Mar 29, 2021 at 01:08:22PM +0100, Richard Fitzgerald wrote:
>> The existing code attempted to handle numbers by doing a strto[u]l(),
>> ignoring the field width, and then repeatedly dividing to extract the
>> field out of the full converted value. If the string contains a run of
>> valid digits longer than will fit in a long or long long, this would
>> overflow and no amount of dividing can recover the correct value.
>>
>> This patch fixes vsscanf() to obey number field widths when parsing
>> the number.
>>
>> A new _parse_integer_limit() is added that takes a limit for the number
>> of characters to parse. The number field conversion in vsscanf is changed
>> to use this new function.
>>
>> If a number starts with a radix prefix, the field width must be long
>> enough for at last one digit after the prefix. If not, it will be handled
>> like this:
>>
>> sscanf("0x4", "%1i", &i): i=0, scanning continues with the 'x'
>> sscanf("0x4", "%2i", &i): i=0, scanning continues with the '4'
>>
>> This is consistent with the observed behaviour of userland sscanf.
>>
>> Note that this patch does NOT fix the problem of a single field value
>> overflowing the target type. So for example:
>>
>> sscanf("123456789abcdef", "%x", &i);
>>
>> Will not produce the correct result because the value obviously overflows
>> INT_MAX. But sscanf will report a successful conversion.
>>
>> Note that where a very large number is used to mean "unlimited", the value
>> INT_MAX is used for consistency with the behaviour of vsnprintf().
>
> ...
>
>> unsigned long simple_strtoul(const char *cp, char **endp, unsigned int base)
>> {
>> - return simple_strtoull(cp, endp, base);
>> + return simple_strntoull(cp, INT_MAX, endp, base);
>
> Why do you need this change?
>
I agree it's not necessary. I changed it between V1 and V2 but I can't
remember what the reason was.
next prev parent reply other threads:[~2021-03-29 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 12:08 [PATCH v7 1/4] lib: vsprintf: scanf: Negative number must have field width > 1 Richard Fitzgerald
2021-03-29 12:08 ` [PATCH v7 2/4] lib: vsprintf: Fix handling of number field widths in vsscanf Richard Fitzgerald
2021-03-29 13:36 ` Andy Shevchenko
2021-03-29 16:27 ` Richard Fitzgerald [this message]
2021-03-29 12:08 ` [PATCH v7 3/4] lib: test_scanf: Add tests for sscanf number conversion Richard Fitzgerald
2021-03-29 12:08 ` [PATCH v7 4/4] selftests: lib: Add wrapper script for test_scanf Richard Fitzgerald
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=9741fc05-52e2-378a-a7ce-9a3fff7c1340@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=patches@opensource.cirrus.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=shuah@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