From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,zkabelac@redhat.com,urezki@gmail.com,stable@vger.kernel.org,sj@kernel.org,hch@lst.de,hch@infradead.org,mpatocka@redhat.com,akpm@linux-foundation.org
Subject: + mm-allow-__gfp_retry_mayfail-in-vmalloc.patch added to mm-hotfixes-unstable branch
Date: Thu, 12 Feb 2026 08:42:42 -0800 [thread overview]
Message-ID: <20260212164242.B6AA1C4CEF7@smtp.kernel.org> (raw)
The patch titled
Subject: mm: allow __GFP_RETRY_MAYFAIL in vmalloc
has been added to the -mm mm-hotfixes-unstable branch. Its filename is
mm-allow-__gfp_retry_mayfail-in-vmalloc.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-allow-__gfp_retry_mayfail-in-vmalloc.patch
This patch will later appear in the mm-hotfixes-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via various
branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there most days
------------------------------------------------------
From: Mikulas Patocka <mpatocka@redhat.com>
Subject: mm: allow __GFP_RETRY_MAYFAIL in vmalloc
Date: Thu, 12 Feb 2026 17:33:30 +0100 (CET)
The commit 07003531e03c8 ("mm/vmalloc: warn on invalid vmalloc gfp flags")
breaks the device mapper VDO target. The VDO target calls vmalloc with
__GFP_RETRY_MAYFAIL and this flag is not in the mask of allowed flags.
There is no reason why vmalloc couldn't support __GFP_RETRY_MAYFAIL, so
let's add this flag to GFP_VMALLOC_SUPPORTED.
Link: https://lkml.kernel.org/r/ff48283b-be21-7f9a-d616-e303a4a1ebe6@redhat.com
Fixes: 07003531e03c ("mm/vmalloc: warn on invalid vmalloc gfp flags")
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Reported-by: Zdenek Kabelac <zkabelac@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Christoph Hellwig <hch@lst.de>
Cc: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
Cc: SeongJae Park <sj@kernel.org>
Cc: <stable@vger.kernel.org> [6.19]
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/vmalloc.c | 1 +
1 file changed, 1 insertion(+)
--- a/mm/vmalloc.c~mm-allow-__gfp_retry_mayfail-in-vmalloc
+++ a/mm/vmalloc.c
@@ -3928,6 +3928,7 @@ fail:
*/
#define GFP_VMALLOC_SUPPORTED (GFP_KERNEL | GFP_ATOMIC | GFP_NOWAIT |\
__GFP_NOFAIL | __GFP_ZERO | __GFP_NORETRY |\
+ __GFP_RETRY_MAYFAIL |\
GFP_NOFS | GFP_NOIO | GFP_KERNEL_ACCOUNT |\
GFP_USER | __GFP_NOLOCKDEP)
_
Patches currently in -mm which might be from mpatocka@redhat.com are
mm-allow-__gfp_retry_mayfail-in-vmalloc.patch
reply other threads:[~2026-02-12 16:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260212164242.B6AA1C4CEF7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=mm-commits@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=sj@kernel.org \
--cc=stable@vger.kernel.org \
--cc=urezki@gmail.com \
--cc=zkabelac@redhat.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