Skip to contentSkip to conversation

mm-huge_memory-skip-invalid-debugfs-new_order-input-for-folio-split.patch removed from -mm tree

merged mm-stable Andrew Morton 1 participant 1 message Mar 12, 2024

lore
Share & tools
lore

Andrew Morton

author tree notice Applied
#0 lore raw

The quilt patch titled
Subject: mm/huge_memory: skip invalid debugfs new_order input for folio split
has been removed from the -mm tree. Its filename was
mm-huge_memory-skip-invalid-debugfs-new_order-input-for-folio-split.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: Zi Yan <[email protected]>
Subject: mm/huge_memory: skip invalid debugfs new_order input for folio split
Date: Thu, 7 Mar 2024 13:18:54 -0500

User can put arbitrary new_order via debugfs for folio split test. Although new_order check is added to split_huge_page_to_list_order() in the prior commit, these two additional checks can avoid unnecessary folio locking and split_folio_to_order() calls.

---

 mm/huge_memory.c |    6 ++++++
 1 file changed, 6 insertions(+)
mm/huge_memory.c renamed from mm/huge_memory.c~mm-huge_memory-skip-invalid-debugfs-new_order-input-for-folio-split +6 -0
@@ -3486,6 +3486,9 @@ static int split_huge_pages_pid(int pid,
 		if (!is_transparent_hugepage(folio))
 			goto next;
 
+		if (new_order >= folio_order(folio))
+			goto next;
+
 		total++;
 		/*
 		 * For folios with private, split_huge_page_to_list_to_order()
@@ -3553,6 +3556,9 @@ static int split_huge_pages_in_file(cons
 		total++;
 		nr_pages = folio_nr_pages(folio);
 
+		if (new_order >= folio_order(folio))
+			goto next;
+
 		if (!folio_trylock(folio))
 			goto next;
 

_

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