Skip to contentSkip to conversation

mm-debug_page_alloc-fix-type-mismatch-for-debug_guardpage_minorder.patch removed from -mm tree

merged mm-stable Andrew Morton 1 participant 1 message Aug 25

lore
Share & tools
lore

Andrew Morton

author tree notice Applied
#0 lore raw

The quilt patch titled
Subject: mm: debug_page_alloc: fix type mismatch for debug_guardpage_minorder
has been removed from the -mm tree. Its filename was
mm-debug_page_alloc-fix-type-mismatch-for-debug_guardpage_minorder.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: Ye Liu <[email protected]>
Subject: mm: debug_page_alloc: fix type mismatch for debug_guardpage_minorder
Date: Wed, 5 Aug 2026 17:31:07 +0800

The debug_guardpage_minorder local variable is declared as unsigned int, but debug_guardpage_minorder_setup() uses unsigned long and kstrtoul() to parse the value.

Use kstrtouint() with unsigned int local variable to match the actual type of _debug_guardpage_minorder. Also fix the format specifier from %lu to %u accordingly.

---

 mm/debug_page_alloc.c |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
mm/debug_page_alloc.c renamed from mm/debug_page_alloc.c~mm-debug_page_alloc-fix-type-mismatch-for-debug_guardpage_minorder +3 -3
@@ -20,14 +20,14 @@ early_param("debug_pagealloc", early_deb
 
 static int __init debug_guardpage_minorder_setup(char *buf)
 {
-	unsigned long res;
+	unsigned int res;
 
-	if (kstrtoul(buf, 10, &res) < 0 ||  res > MAX_PAGE_ORDER / 2) {
+	if (kstrtouint(buf, 10, &res) < 0 ||  res > MAX_PAGE_ORDER / 2) {
 		pr_err("Bad debug_guardpage_minorder value: %s\n", buf);
 		return 0;
 	}
 	_debug_guardpage_minorder = res;
-	pr_info("Setting debug_guardpage_minorder to %lu\n", res);
+	pr_info("Setting debug_guardpage_minorder to %u\n", res);
 	return 0;
 }
 early_param("debug_guardpage_minorder", debug_guardpage_minorder_setup);

_

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