From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Petr Mladek <pmladek@suse.com>
Cc: 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>,
David Laight <david.laight.linux@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/2] lib/vsprintf: Fixes size check
Date: Thu, 7 May 2026 16:37:03 +0900 [thread overview]
Message-ID: <20260507163703.2de07cc10a1eacbe00cc5e28@kernel.org> (raw)
In-Reply-To: <afmsZHDYr1iL4S6v@pathway.suse.cz>
On Tue, 5 May 2026 10:37:56 +0200
Petr Mladek <pmladek@suse.com> wrote:
> On Thu 2026-03-26 21:11:50, Masami Hiramatsu (Google) wrote:
> > Hi,
> >
> > Here is the 6th version of patches to fix vsnprintf().
> >
> > - Fix to limit the size of width and precision.
> > - Warn if the return size is over INT_MAX.
> >
> > Previous version is here;
> >
> > https://lore.kernel.org/all/177444525139.185641.12184379647176430297.stgit@devnote2/
> >
> > This version just makes function header and WARN_ONCE() to one line[1/2].
> > No functional change.
> >
> > Thank you,
> >
> > ---
> >
> > Masami Hiramatsu (Google) (2):
> > lib/vsprintf: Fix to check field_width and precision
> > lib/vsprintf: Limit the returning size to INT_MAX
>
> JFYI, the patchset has been commited into printk/linux.git,
> branch for-7.2-vsprintf-size-checks.
Got it, Thank you!
>
> Best Regards,
> Petr
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2026-05-07 7:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <177452711082.197965.4952719534268072174.stgit@devnote2>
2026-05-04 15:08 ` [PATCH v6 0/2] lib/vsprintf: Fixes size check Petr Mladek
2026-05-05 8:37 ` Petr Mladek
2026-05-07 7:37 ` Masami Hiramatsu [this message]
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=20260507163703.2de07cc10a1eacbe00cc5e28@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