Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: rostedt@goodmis.org, sergey.senozhatsky@gmail.com,
	shuah@kernel.org, patches@opensource.cirrus.com,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 2/4] lib: vsprintf: Fix handling of number field widths in vsscanf
Date: Mon, 21 Dec 2020 16:19:35 +0100	[thread overview]
Message-ID: <X+C9Bw9KtOdRuuBJ@alley> (raw)
In-Reply-To: <20201217180057.23786-2-rf@opensource.cirrus.com>

On Thu 2020-12-17 18:00:55, 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.
> 
> Signed-off-by: Richard Fitzgerald <rf@opensource.cirrus.com>

Reviewed-by: Petr Mladek <pmladek@suse.com>

Best Regards,
Petr

  reply	other threads:[~2020-12-21 15:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 18:00 [PATCH v3 1/4] lib: vsprintf: scanf: Negative number must have field width > 1 Richard Fitzgerald
2020-12-17 18:00 ` [PATCH v3 2/4] lib: vsprintf: Fix handling of number field widths in vsscanf Richard Fitzgerald
2020-12-21 15:19   ` Petr Mladek [this message]
2020-12-17 18:00 ` [PATCH v3 3/4] lib: test_scanf: Add tests for sscanf number conversion Richard Fitzgerald
2020-12-21 15:21   ` Petr Mladek
2020-12-17 18:00 ` [PATCH v3 4/4] selftests: lib: Add wrapper script for test_scanf Richard Fitzgerald
2020-12-21 15:16 ` [PATCH v3 1/4] lib: vsprintf: scanf: Negative number must have field width > 1 Petr Mladek
2021-01-11 10:25 ` Petr Mladek
2021-01-11 10:36   ` Andy Shevchenko
2021-01-11 10:39     ` Richard Fitzgerald
2021-01-11 10:43       ` Richard Fitzgerald
2021-01-11 11:14         ` Andy Shevchenko
2021-01-11 10:37   ` Richard Fitzgerald
2021-01-11 11:15     ` Andy Shevchenko

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=X+C9Bw9KtOdRuuBJ@alley \
    --to=pmladek@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.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