From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: David Laight <david.laight.linux@gmail.com>
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 v2 1/2] lib/vsprintf: Fix to check field_width and precision
Date: Sat, 21 Mar 2026 22:07:12 +0900 [thread overview]
Message-ID: <20260321220712.2845dfa860a03bbd837a8fe3@kernel.org> (raw)
In-Reply-To: <20260320094858.36979c73@pumpkin>
On Fri, 20 Mar 2026 09:48:58 +0000
David Laight <david.laight.linux@gmail.com> wrote:
> On Fri, 20 Mar 2026 12:54:48 +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>
> > ---
> > Changes in v2:
> > - Fix to use logical split.
> > ---
> > lib/vsprintf.c | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/lib/vsprintf.c b/lib/vsprintf.c
> > index 800b8ac49f53..32a164e2adf4 100644
> > --- a/lib/vsprintf.c
> > +++ b/lib/vsprintf.c
> > @@ -2803,7 +2803,8 @@ 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)) {
> > + if (WARN_ONCE(spec->field_width > FIELD_WIDTH_MAX || spec->field_width < -FIELD_WIDTH_MAX,
>
> Check and update width before the assignment to spec->field_width.
>
> David
Indeed. I'll do the same for precision.
Thanks,
>
> > + "field width %d too large", width)) {
> > spec->field_width = clamp(width, -FIELD_WIDTH_MAX, FIELD_WIDTH_MAX);
> > }
> > }
> > @@ -2812,7 +2813,8 @@ static void
> > set_precision(struct printf_spec *spec, int prec)
> > {
> > spec->precision = prec;
> > - if (WARN_ONCE(spec->precision != prec, "precision %d too large", prec)) {
> > + if (WARN_ONCE(spec->precision > PRECISION_MAX || spec->precision < 0,
> > + "precision %d too large", prec)) {
> > spec->precision = clamp(prec, 0, PRECISION_MAX);
> > }
> > }
> >
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2026-03-21 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 3:54 [PATCH v2 0/2] lib/vsprintf: Fixes size check Masami Hiramatsu (Google)
2026-03-20 3:54 ` [PATCH v2 1/2] lib/vsprintf: Fix to check field_width and precision Masami Hiramatsu (Google)
2026-03-20 9:48 ` David Laight
2026-03-21 13:07 ` Masami Hiramatsu [this message]
2026-03-20 3:54 ` [PATCH v2 2/2] lib/vsprintf: Limit the returning size to INT_MAX Masami Hiramatsu (Google)
2026-03-20 16:51 ` Petr Mladek
2026-03-21 14:16 ` Masami Hiramatsu
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=20260321220712.2845dfa860a03bbd837a8fe3@kernel.org \
--to=mhiramat@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=david.laight.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--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
Powered by JetHome