From: Uladzislau Rezki <urezki@gmail.com>
To: Baoquan He <bhe@redhat.com>
Cc: "Uladzislau Rezki (Sony)" <urezki@gmail.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] mm/vmalloc, mm/kasan: respect gfp mask in kasan_populate_vmalloc()
Date: Mon, 1 Sep 2025 12:23:34 +0200 [thread overview]
Message-ID: <aLV0JrSPfitu1jFV@pc638.lan> (raw)
In-Reply-To: <aLVyia16eyoYftAw@MiWiFi-R3L-srv>
On Mon, Sep 01, 2025 at 06:16:41PM +0800, Baoquan He wrote:
> Hi Uladzislau,
>
> On 08/31/25 at 02:10pm, Uladzislau Rezki (Sony) wrote:
> > kasan_populate_vmalloc() and its helpers ignore the caller's gfp_mask
> > and always allocate memory using the hardcoded GFP_KERNEL flag. This
> > makes them inconsistent with vmalloc(), which was recently extended to
> > support GFP_NOFS and GFP_NOIO allocations.
>
> Is this patch on top of your patchset "[PATCH 0/8] __vmalloc() and no-block
> support"? Or it is a replacement of "[PATCH 5/8] mm/kasan, mm/vmalloc: Respect
> GFP flags in kasan_populate_vmalloc()" in the patchset?
>
> I may not get their relationship clearly.
>
It is out of series which i posted to support no-block for vmalloc.
I will base a new version based on this patch because it is rather
a fix.
It is to address and complete GFP_NOFS/GFP_NOIO flags for vmalloc.
--
Uladzislau Rezki
next prev parent reply other threads:[~2025-09-01 10:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 12:10 [PATCH] mm/vmalloc, mm/kasan: respect gfp mask in kasan_populate_vmalloc() Uladzislau Rezki (Sony)
2025-08-31 12:12 ` Uladzislau Rezki
2025-08-31 19:24 ` Andrew Morton
2025-09-01 10:00 ` Uladzislau Rezki
2025-09-05 14:25 ` Andrey Ryabinin
2025-09-01 10:16 ` Baoquan He
2025-09-01 10:23 ` Uladzislau Rezki [this message]
2025-09-01 15:33 ` Baoquan He
2025-09-05 14:35 ` Andrey Ryabinin
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=aLV0JrSPfitu1jFV@pc638.lan \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=stable@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.