From: David Laight <david.laight.linux@gmail.com>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] lib/vsprintf: Fix to check field_width and precision
Date: Wed, 25 Mar 2026 10:00:09 +0000 [thread overview]
Message-ID: <20260325100009.42871082@pumpkin> (raw)
In-Reply-To: <177440551685.147866.4375769344976474036.stgit@devnote2>
On Wed, 25 Mar 2026 11:25:16 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> Check the field_width and presition correctly. Previously it depends
> on the bitfield conversion from int to check out-of-range error.
> However, commit 938df695e98d ("vsprintf: associate the format state
> with the format pointer") changed those fields to int.
> We need to check the out-of-range correctly without bitfield
> conversion.
>
> Fixes: 938df695e98d ("vsprintf: associate the format state with the format pointer")
> Reported-by: David Laight <david.laight.linux@gmail.com>
> Closes: https://lore.kernel.org/all/20260318151250.40fef0ab@pumpkin/
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
I've just read the code - my god is it complicated and confusing.
But I think it looks ok, so:
Reviewed-by: David Laight <david.laight.linux@gmail.com>
Maybe I'll find to time (haha) to rewrite it based on the nolibc version.
It'll be a lot smaller and a lot faster.
I also suspect that corner cases like ("%#.0o", 0) (where the '#' needs to
add a leading zero to the empty string) aren't right.
But that is different from this fix.
David
> ---
> Changes in v4:
> - Do clamp() first.
> - Accept negative precision (this means no precision) .
> - Change the warning message for width.
> Changes in v3:
> - Check and update width and precision before assigning to spec.
> Changes in v2:
> - Fix to use logical split.
> ---
> lib/vsprintf.c | 17 ++++++-----------
> 1 file changed, 6 insertions(+), 11 deletions(-)
>
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
> index 800b8ac49f53..5fa8f69030be 100644
> --- a/lib/vsprintf.c
> +++ b/lib/vsprintf.c
> @@ -2679,9 +2679,6 @@ struct fmt format_decode(struct fmt fmt, struct printf_spec *spec)
>
> /* we finished early by reading the precision */
> if (unlikely(fmt.state == FORMAT_STATE_PRECISION)) {
> - if (spec->precision < 0)
> - spec->precision = 0;
> -
> fmt.state = FORMAT_STATE_NONE;
> goto qualifier;
> }
> @@ -2802,19 +2799,17 @@ struct fmt format_decode(struct fmt fmt, struct printf_spec *spec)
> static void
> set_field_width(struct printf_spec *spec, int width)
> {
> - spec->field_width = width;
> - if (WARN_ONCE(spec->field_width != width, "field width %d too large", width)) {
> - spec->field_width = clamp(width, -FIELD_WIDTH_MAX, FIELD_WIDTH_MAX);
> - }
> + spec->field_width = clamp(width, -FIELD_WIDTH_MAX, FIELD_WIDTH_MAX);
> + WARN_ONCE(spec->field_width != width, "field width %d out of range",
> + width);
> }
>
> static void
> set_precision(struct printf_spec *spec, int prec)
> {
> - spec->precision = prec;
> - if (WARN_ONCE(spec->precision != prec, "precision %d too large", prec)) {
> - spec->precision = clamp(prec, 0, PRECISION_MAX);
> - }
> + /* We allow negative precision, but treat it as if there was no precision. */
> + spec->precision = clamp(prec, -1, PRECISION_MAX);
> + WARN_ONCE(spec->precision < prec, "precision %d too large", prec);
> }
>
> /*
>
next prev parent reply other threads:[~2026-03-25 10:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 2:25 [PATCH v4 0/2] lib/vsprintf: Fixes size check Masami Hiramatsu (Google)
2026-03-25 2:25 ` [PATCH v4 1/2] lib/vsprintf: Fix to check field_width and precision Masami Hiramatsu (Google)
2026-03-25 10:00 ` David Laight [this message]
2026-03-25 10:22 ` Petr Mladek
2026-03-25 11:29 ` David Laight
2026-03-25 15:10 ` David Laight
2026-03-25 13:30 ` Masami Hiramatsu
2026-03-25 13:27 ` Masami Hiramatsu
2026-03-25 2:25 ` [PATCH v4 2/2] lib/vsprintf: Limit the returning size to INT_MAX Masami Hiramatsu (Google)
2026-03-25 5:04 ` [PATCH v4 0/2] lib/vsprintf: Fixes size check Andrew Morton
2026-03-25 5:41 ` Masami Hiramatsu
2026-03-25 10:20 ` David Laight
2026-03-26 7:39 ` Masami Hiramatsu
2026-03-26 9:12 ` David Laight
2026-03-27 7:28 ` Masami Hiramatsu
2026-03-27 10:12 ` David Laight
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=20260325100009.42871082@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mhiramat@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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