[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20260108094242.8b043d248e7877235f606416@linux-foundation.org>
Date: Thu, 8 Jan 2026 09:42:42 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Kees Cook <kees@...nel.org>
Cc: Dmitry Antipov <dmantipov@...dex.ru>, Carlos Maiolino <cem@...nel.org>,
Christoph Hellwig <hch@...radead.org>, Andy Shevchenko <andy@...nel.org>,
linux-xfs@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH v3 1/2] lib: introduce simple error-checking wrapper for
memparse()
On Thu, 8 Jan 2026 09:06:49 -0800 Kees Cook <kees@...nel.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@...radead.org>
> > Suggested-by: Kees Cook <kees@...nel.org>
> > Signed-off-by: Dmitry Antipov <dmantipov@...dex.ru>
>
> LGTM, thanks!
>
> Reviewed-by: Kees Cook <kees@...nel.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!
Powered by blists - more mailing lists