From: Kees Cook <kees@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dmitry Antipov <dmantipov@yandex.ru>,
Carlos Maiolino <cem@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Andy Shevchenko <andy@kernel.org>,
linux-xfs@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v3 1/2] lib: introduce simple error-checking wrapper for memparse()
Date: Thu, 8 Jan 2026 09:55:27 -0800 [thread overview]
Message-ID: <202601080954.272AAE6217@keescook> (raw)
In-Reply-To: <20260108094242.8b043d248e7877235f606416@linux-foundation.org>
On Thu, Jan 08, 2026 at 09:42:42AM -0800, Andrew Morton wrote:
> On Thu, 8 Jan 2026 09:06:49 -0800 Kees Cook <kees@kernel.org> wrote:
>
> > On Thu, Jan 08, 2026 at 07:52:15PM +0300, Dmitry Antipov wrote:
> > > Introduce 'memvalue()' which uses 'memparse()' to parse a string
> > > with optional memory suffix into a non-negative number. If parsing
> > > has succeeded, returns 0 and stores the result at the location
> > > specified by the second argument. Otherwise returns -EINVAL and
> > > leaves the location untouched.
> > >
> > > Suggested-by: Christoph Hellwig <hch@infradead.org>
> > > Suggested-by: Kees Cook <kees@kernel.org>
> > > Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
> >
> > LGTM, thanks!
> >
> > Reviewed-by: Kees Cook <kees@kernel.org>
>
> Thanks, I'll add both these to mm.git's mm-nonmm-unstable branch for
> testing.
>
> If XFS people would prefer to take [2/2] via the xfs tree then please
> lmk and I'll send it over when [1/2] is upstreamed. Or we can take
> both patches via the xfs tree. Or something. Sending out an acked-by:
> would be simplest!
I assumed this would go via xfs tree, but I'm happy to do whatever.
--
Kees Cook
next prev parent reply other threads:[~2026-01-08 17:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 16:52 [PATCH v3 1/2] lib: introduce simple error-checking wrapper for memparse() Dmitry Antipov
2026-01-08 16:52 ` [PATCH v3 2/2] xfs: adjust handling of a few numerical mount options Dmitry Antipov
2026-01-08 17:06 ` [PATCH v3 1/2] lib: introduce simple error-checking wrapper for memparse() Kees Cook
2026-01-08 17:42 ` Andrew Morton
2026-01-08 17:55 ` Kees Cook [this message]
2026-01-09 12:53 ` Carlos Maiolino
2026-01-08 20:05 ` Andy Shevchenko
2026-01-09 11:41 ` Dmitry Antipov
2026-01-09 17:09 ` Andy Shevchenko
2026-01-09 17:11 ` Andy Shevchenko
2026-01-11 0:01 ` Andrew Morton
2026-01-08 20:10 ` Andy Shevchenko
2026-01-09 11:05 ` Dmitry Antipov
2026-01-09 11:18 ` Andy Shevchenko
2026-01-20 0:06 ` Andrew Morton
2026-01-20 14:12 ` [PATCH v4 1/3] " Dmitry Antipov
2026-01-20 14:12 ` [PATCH v4 2/3] lib: fix a few comments to match kernel-doc -Wreturn style Dmitry Antipov
2026-01-20 14:47 ` Andy Shevchenko
2026-01-20 14:12 ` [PATCH v4 3/3] xfs: adjust handling of a few numerical mount options Dmitry Antipov
2026-01-20 14:59 ` Andy Shevchenko
2026-01-20 16:57 ` Dmitry Antipov
2026-01-20 21:49 ` Andy Shevchenko
2026-01-20 22:55 ` Darrick J. Wong
2026-01-21 5:21 ` Dmitry Antipov
2026-01-21 13:25 ` Andy Shevchenko
2026-01-20 14:45 ` [PATCH v4 1/3] lib: introduce simple error-checking wrapper for memparse() Andy Shevchenko
2026-01-20 14:46 ` 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=202601080954.272AAE6217@keescook \
--to=kees@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andy@kernel.org \
--cc=cem@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=hch@infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox