From: Uladzislau Rezki <urezki@gmail.com>
To: Vlastimil Babka <vbabka@suse.com>
Cc: "Uladzislau Rezki (Sony)" <urezki@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org,
"Harry Yoo (Oracle)" <harry@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Hao Li <hao.li@linux.dev>
Subject: Re: [PATCH 1/2] mm/slab: Add kvfree_atomic() helper
Date: Wed, 29 Apr 2026 10:58:46 +0200 [thread overview]
Message-ID: <afHIRrqj20hCMily@milan> (raw)
In-Reply-To: <2d996917-60bb-4ef9-b397-65decf3b296d@suse.com>
On Wed, Apr 29, 2026 at 10:28:02AM +0200, Vlastimil Babka wrote:
> +Cc SLAB maintainers. Please use get_maintainers.pl next time.
>
> On 4/28/26 18:14, Uladzislau Rezki (Sony) wrote:
> > kvmalloc() now supports non-sleeping GFP flags, including
> > the vmalloc fallback path. This means it may return vmalloc
> > memory even for GFP_ATOMIC and GFP_NOWAIT allocations.
> >
> > Freeing such memory with kvfree() may then end up calling
> > vfree(), which is not safe for non-sleeping contexts.
> >
> > Introduce kvfree_atomic() helper for such cases. It mirrors
> > kvfree(), but uses vfree_atomic() for vmalloced memory.
> >
> > Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
>
> Acked-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
>
Thank you and thank you for adding SLAB maintainers!
--
Uladzislau Rezki
next prev parent reply other threads:[~2026-04-29 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 16:14 [PATCH 1/2] mm/slab: Add kvfree_atomic() helper Uladzislau Rezki (Sony)
2026-04-28 16:14 ` [PATCH 2/2] rhashtable: Add bucket_table_free_atomic() helper Uladzislau Rezki (Sony)
2026-04-29 8:28 ` [PATCH 1/2] mm/slab: Add kvfree_atomic() helper Vlastimil Babka
2026-04-29 8:58 ` Uladzislau Rezki [this message]
2026-04-29 11:19 ` Harry Yoo (Oracle)
2026-05-05 9:30 ` Herbert Xu
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=afHIRrqj20hCMily@milan \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hao.li@linux.dev \
--cc=harry@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vbabka@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