The quilt patch titled Subject: mm/compaction: set compact_cached_free_pfn correctly in update_pageblock_skip has been removed from the -mm tree. Its filename was mm-compaction-set-compact_cached_free_pfn-correctly-in-update_pageblock_skip.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: Kemeng Shi <shikemeng@xxxxxxxxxxxxxxx> Subject: mm/compaction: set compact_cached_free_pfn correctly in update_pageblock_skip Date: Thu, 3 Aug 2023 17:48:58 +0800 Patch series "Fixes and cleanups to compaction", v2. This series contains random fixes and cleanups to free page isolation in compaction. This is based on another compact series[1]. More details can be found in respective patches. This patch (of 4): We will set skip to page block of block_start_pfn, it's more reasonable to set compact_cached_free_pfn to page block before the block_start_pfn. Link: https://lkml.kernel.org/r/20230803094901.2915942-1-shikemeng@xxxxxxxxxxxxxxx Link: https://lkml.kernel.org/r/20230803094901.2915942-2-shikemeng@xxxxxxxxxxxxxxx Signed-off-by: Kemeng Shi <shikemeng@xxxxxxxxxxxxxxx> Reviewed-by: Baolin Wang <baolin.wang@xxxxxxxxxxxxxxxxx> Cc: David Hildenbrand <david@xxxxxxxxxx> Cc: Mel Gorman <mgorman@xxxxxxxxxxxxxxxxxxx> Cc: Kemeng Shi <shikemeng@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/compaction.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --- a/mm/compaction.c~mm-compaction-set-compact_cached_free_pfn-correctly-in-update_pageblock_skip +++ a/mm/compaction.c @@ -1717,7 +1717,8 @@ static void isolate_freepages(struct com /* Update the skip hint if the full pageblock was scanned */ if (isolate_start_pfn == block_end_pfn) - update_pageblock_skip(cc, page, block_start_pfn); + update_pageblock_skip(cc, page, block_start_pfn - + pageblock_nr_pages); /* Are enough freepages isolated? */ if (cc->nr_freepages >= cc->nr_migratepages) { _ Patches currently in -mm which might be from shikemeng@xxxxxxxxxxxxxxx are