mm-migrate-use-thp_order-instead-of-hpage_pmd_order-for-new-page-allocation.patch removed from -mm tree
The patch titled
Subject: mm: migrate: use thp_order instead of HPAGE_PMD_ORDER for new page allocation.
has been removed from the -mm tree. Its filename was
mm-migrate-use-thp_order-instead-of-hpage_pmd_order-for-new-page-allocation.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Zi Yan <[email protected]>
Subject: mm: migrate: use thp_order instead of HPAGE_PMD_ORDER for new page allocation.
Fix a VM_BUG_ON_FOLIO(folio_nr_pages(old) != nr_pages) crash.
With folios support, it is possible to have other than HPAGE_PMD_ORDER THPs, in the form of folios, in the system. Use thp_order() to correctly determine the source page order during migration.
---
mm/mempolicy.c | 2 +- mm/migrate.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
mm/mempolicy.c renamed from mm/mempolicy.c~mm-migrate-use-thp_order-instead-of-hpage_pmd_order-for-new-page-allocation +1 -1
@@ -1209,7 +1209,7 @@ static struct page *new_page(struct pagestruct page *thp; thp =alloc_hugepage_vma (GFP_TRANSHUGE , vma, address, -HPAGE_PMD_ORDER ); +thp_order (page));if (!thp)return NULL ;prep_transhuge_page (thp);
mm/migrate.c renamed from mm/migrate.c~mm-migrate-use-thp_order-instead-of-hpage_pmd_order-for-new-page-allocation +1 -1
@@ -1547,7 +1547,7 @@ struct page *alloc_migration_target(stru*/ gfp_mask &= ~__GFP_RECLAIM; gfp_mask |=GFP_TRANSHUGE ; - order =HPAGE_PMD_ORDER ; + order =thp_order (page); } zidx =zone_idx (page_zone (page));if (is_highmem_idx (zidx) || zidx ==ZONE_MOVABLE )
_
Patches currently in -mm which might be from [email protected] are
mm-page_alloc-simplify-pageblock-migratetype-check-in-__free_one_page.patch mm-wrap-__find_buddy_pfn-with-a-necessary-buddy-page-validation.patch mm-wrap-__find_buddy_pfn-with-a-necessary-buddy-page-validation-v4.patch