mm-page_alloc-relax-gfp-warn-in-nolock-allocs.patch removed from -mm tree
The quilt patch titled
Subject: mm/page_alloc: relax GFP WARN in nolock allocs
has been removed from the -mm tree. Its filename was
mm-page_alloc-relax-gfp-warn-in-nolock-allocs.patch
This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Brendan Jackman <[email protected]>
Subject: mm/page_alloc: relax GFP WARN in nolock allocs
Date: Fri, 03 Jul 2026 12:31:46 +0000
This WARN forbids setting other flags than __GFP_ACCOUNT but we unconditionally set the ones in gfp_nolock so they are certainly fine for the caller to set.
There are other GFP flags that are almost certainly fine to set here; Willy noted GFP_HIGHMEM, GFP_DMA, GFP_MOVABLE and GFP_HARDWALL. But, nolock allocation is rather special, so be conservative to try and ensure we have a chance to think carefully before nontrivial new usecases arise.
---
mm/page_alloc.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
mm/page_alloc.c renamed from mm/page_alloc.c~mm-page_alloc-relax-gfp-warn-in-nolock-allocs +2 -1
@@ -5355,7 +5355,8 @@ struct page *__alloc_frozen_pages_noprofreturn NULL ;if (alloc_flags &ALLOC_NOLOCK ) { -VM_WARN_ON_ONCE (gfp & ~__GFP_ACCOUNT); +/* Certain other flags could be supported later if needed. */ +VM_WARN_ON_ONCE (gfp & ~(__GFP_ACCOUNT | gfp_nolock));if (!alloc_nolock_allowed ())return NULL ; gfp |= gfp_nolock;
_
Patches currently in -mm which might be from [email protected] are
mm-secretmem-dont-allow-highmem-folios.patch mm-page_alloc-dont-spin_trylock-in-nmi-on-up.patch mm-page_alloc-dont-spin_trylock-when-disallowed-in-free_one_page.patch mm-page_alloc-rename-fpi_trylock-fpi_nolock.patch cgroup-cpuset-update-some-comments-about-the-page-allocator.patch mm-page_alloc-fixup-alloc_pages_nolock_noprof-comment.patch mm-page_alloc-remove-a-couple-of-vm_bug_onst.patch