[moderation/CI] Re: mm: ASI direct map management

[syzbot ci]

syzbot ci has tested the following series

[v1] mm: ASI direct map management
https://lore.kernel.org/all/20250924-b4-asi-page-a...@google.com
* [PATCH 01/21] x86/mm/asi: Add CONFIG_MITIGATION_ADDRESS_SPACE_ISOLATION
* [PATCH 02/21] x86/mm/asi: add X86_FEATURE_ASI and asi=
* [PATCH 03/21] x86/mm: factor out phys_pgd_init()
* [PATCH 04/21] x86/mm/asi: set up asi_nonsensitive_pgd
* [PATCH 05/21] x86/mm/pat: mirror direct map changes to ASI
* [PATCH 06/21] mm/page_alloc: add __GFP_SENSITIVE and always set it
* [PATCH 07/21] mm: introduce for_each_free_list()
* [PATCH 08/21] mm: rejig pageblock mask definitions
* [PATCH 09/21] mm/page_alloc: Invert is_check_pages_enabled() check
* [PATCH 10/21] mm/page_alloc: remove ifdefs from pindex helpers
* [PATCH 11/21] mm: introduce freetype_t
* [PATCH 12/21] mm/asi: encode sensitivity in freetypes and pageblocks
* [PATCH 13/21] mm/page_alloc_test: unit test pindex helpers
* [PATCH 14/21] x86/mm/pat: introduce cpa_fault option
* [PATCH 15/21] mm/page_alloc: rename ALLOC_NON_BLOCK back to _HARDER
* [PATCH 16/21] mm/page_alloc: introduce ALLOC_NOBLOCK
* [PATCH 17/21] mm/slub: defer application of gfp_allowed_mask
* [PATCH 18/21] mm/asi: support changing pageblock sensitivity
* [PATCH 19/21] mm/asi: bad_page() when ASI mappings are wrong
* [PATCH 20/21] x86/mm/asi: don't use global pages when ASI enabled
* [PATCH 21/21] mm: asi_test: smoke test for [non]sensitive page allocs

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/c5d6edfc-6999-4b8b-a338-e60860e51a28

***

kernel build error

tree: linux-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base: ce7f1a983b074f6cf8609068088ca3182c569ee4
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/e0b7d7f4-8eca-4d2b-aa86-2950c847524b/config

mm/compaction.c:2319:7: error: use of undeclared identifier 'migratetype'; did you mean 'migrate_pfn'?

***

If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syz...@syzkaller.appspotmail.com

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzk...@googlegroups.com.

The email will later be sent to:
[ak...@linux-foundation.org axelra...@google.com b...@alien8.de dave....@linux.intel.com da...@redhat.com derk...@google.com han...@cmpxchg.org jack...@google.com jun...@google.com liam.h...@oracle.com linux-...@vger.kernel.org linu...@kvack.org lorenzo...@oracle.com lu...@kernel.org mho...@suse.com mi...@redhat.com pet...@infradead.org rei...@google.com rien...@google.com roman.g...@linux.dev rp...@kernel.org sur...@google.com tg...@linutronix.de vba...@suse.cz x...@kernel.org yosry...@linux.dev yua...@google.com z...@nvidia.com]

If the report looks fine to you, reply with:
#syz upstream