Skip to contentSkip to conversation

mm-memremap-reject-unreasonable-folio-compound-page-sizes-in-memremap_pages.patch removed from -mm tree

merged mm-stable Andrew Morton 1 participant 1 message Sep 21, 2025

lore
Share & tools
lore

Andrew Morton

author tree notice Applied
#0 lore raw

The quilt patch titled
Subject: mm/memremap: reject unreasonable folio/compound page sizes in memremap_pages()
has been removed from the -mm tree. Its filename was
mm-memremap-reject-unreasonable-folio-compound-page-sizes-in-memremap_pages.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: David Hildenbrand <[email protected]>
Subject: mm/memremap: reject unreasonable folio/compound page sizes in memremap_pages()
Date: Mon, 1 Sep 2025 17:03:28 +0200

Let's reject unreasonable folio sizes early, where we can still fail. We'll add sanity checks to prepare_compound_head/prepare_compound_page next.

Is there a way to configure a system such that unreasonable folio sizes would be possible? It would already be rather questionable.

If so, we'd probably want to bail out earlier, where we can avoid a WARN and just report a proper error message that indicates where something went wrong such that we messed up.

---

 mm/memremap.c |    3 +++
 1 file changed, 3 insertions(+)
mm/memremap.c renamed from mm/memremap.c~mm-memremap-reject-unreasonable-folio-compound-page-sizes-in-memremap_pages +3 -0
@@ -275,6 +275,9 @@ void *memremap_pages(struct dev_pagemap
 
 	if (WARN_ONCE(!nr_range, "nr_range must be specified\n"))
 		return ERR_PTR(-EINVAL);
+	if (WARN_ONCE(pgmap->vmemmap_shift > MAX_FOLIO_ORDER,
+		      "requested folio size unsupported\n"))
+		return ERR_PTR(-EINVAL);
 
 	switch (pgmap->type) {
 	case MEMORY_DEVICE_PRIVATE:

_

Patches currently in -mm which might be from [email protected] are