From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Laight <david.laight.linux@gmail.com>,
Kees Cook <kees@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 0/5] lib and lib/cmdline enhancements
Date: Wed, 18 Feb 2026 15:48:57 +0200 [thread overview]
Message-ID: <aZXDSbyH8tWmTPPL@smile.fi.intel.com> (raw)
In-Reply-To: <87799485ed44bf023f0e1a7ed67f2e5268763c73.camel@yandex.ru>
On Wed, Feb 18, 2026 at 04:40:28PM +0300, Dmitry Antipov wrote:
> On Thu, 2026-02-12 at 19:44 +0300, Dmitry Antipov wrote:
>
> > Adjust '_parse_integer_limit()' and 'memparse()' to not ignore
> > overflows, extend string to 64-bit integer conversion tests, add
> > KUnit-based test for 'memparse()' and fix kernel-doc glitches
> > found in lib/cmdline.c.
> >
> > Dmitry Antipov (5):
> > lib: fix _parse_integer_limit() to handle overflow
> > lib: fix memparse() to handle overflow
> > lib: add more string to 64-bit integer conversion overflow tests
> > lib/cmdline_kunit: add test case for memparse()
> > lib/cmdline: adjust a few comments to fix kernel-doc -Wreturn warnings
>
> Any chance to move forward with this?
I think it's a grace period due to ongoing merge window.
Also we need more input on the first patch from others,
perhaps Kees and Andrew can take a look when they will be
less busy.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-18 13:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 16:44 [PATCH v8 0/5] lib and lib/cmdline enhancements Dmitry Antipov
2026-02-12 16:44 ` [PATCH v8 1/5] lib: fix _parse_integer_limit() to handle overflow Dmitry Antipov
2026-02-12 16:44 ` [PATCH v8 2/5] lib: fix memparse() " Dmitry Antipov
2026-02-24 12:32 ` Rodrigo Alencar
2026-02-24 14:15 ` Rodrigo Alencar
2026-02-25 6:58 ` Dmitry Antipov
2026-02-12 16:44 ` [PATCH v8 3/5] lib: add more string to 64-bit integer conversion overflow tests Dmitry Antipov
2026-02-12 16:44 ` [PATCH v8 4/5] lib/cmdline_kunit: add test case for memparse() Dmitry Antipov
2026-02-12 16:44 ` [PATCH v8 5/5] lib/cmdline: adjust a few comments to fix kernel-doc -Wreturn warnings Dmitry Antipov
2026-02-18 13:40 ` [PATCH v8 0/5] lib and lib/cmdline enhancements Dmitry Antipov
2026-02-18 13:48 ` Andy Shevchenko [this message]
2026-04-02 6:56 ` Dmitry Antipov
2026-04-02 8:30 ` Andy Shevchenko
2026-04-02 16:00 ` Andrew Morton
2026-04-02 16:09 ` 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=aZXDSbyH8tWmTPPL@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david.laight.linux@gmail.com \
--cc=djwong@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.