From: Uladzislau Rezki <urezki@gmail.com>
To: Kees Cook <kees@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Shung-Hsi Yu <shung-hsi.yu@suse.com>,
Eduard Zingerman <eddyz87@gmail.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Uladzislau Rezki <urezki@gmail.com>,
Erhard Furtner <erhard_f@mailbox.org>,
Danilo Krummrich <dakr@kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
bpf@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH 0/2] mm: vmalloc: Actually use the in-place vrealloc region
Date: Fri, 16 May 2025 08:32:49 +0200 [thread overview]
Message-ID: <aCbcEWR9RbjFjXV9@pc636> (raw)
In-Reply-To: <20250515214020.work.519-kees@kernel.org>
On Thu, May 15, 2025 at 02:42:14PM -0700, Kees Cook wrote:
> Hi,
>
> This fixes a performance regression[1] with vrealloc(). This needs to
> get into v6.15, which is where the regression originates, and then it'll
> get backport to the -stable releases as well.
>
> Thanks!
>
> -Kees
>
> [1] https://lore.kernel.org/lkml/20250515-bpf-verifier-slowdown-vwo2meju4cgp2su5ckj@6gi6ssxbnfqg/
>
> Kees Cook (2):
> mm: vmalloc: Actually use the in-place vrealloc region
> mm: vmalloc: Only zero-init on vrealloc shrink
>
> mm/vmalloc.c | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
Looks good to me both.
Reviewed-by: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
--
Uladzislau Rezki
next prev parent reply other threads:[~2025-05-16 6:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 21:42 [PATCH 0/2] mm: vmalloc: Actually use the in-place vrealloc region Kees Cook
2025-05-15 21:42 ` [PATCH 1/2] " Kees Cook
2025-05-15 21:42 ` [PATCH 2/2] mm: vmalloc: Only zero-init on vrealloc shrink Kees Cook
2025-05-16 6:02 ` [PATCH 0/2] mm: vmalloc: Actually use the in-place vrealloc region Shung-Hsi Yu
2025-05-16 6:32 ` Uladzislau Rezki [this message]
2025-05-16 8:28 ` Danilo Krummrich
2025-05-19 19:18 ` Kees Cook
2025-05-20 0:06 ` Andrew Morton
2025-05-20 16:06 ` Kees Cook
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=aCbcEWR9RbjFjXV9@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=dakr@kernel.org \
--cc=eddyz87@gmail.com \
--cc=erhard_f@mailbox.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=shung-hsi.yu@suse.com \
/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;
as well as URLs for NNTP newsgroup(s).