[moderation/CI] Re: Introducte Reserved THP

syzbot ci has tested the following series

[v1] Introducte Reserved THP
https://lore.kernel.org/all/[email protected]
* [RFC PATCH 1/8] mm: page_alloc: add reserved THP pageblock type
* [RFC PATCH 2/8] mm: add boot-time reserved THP pageblock capacity
* [RFC PATCH 3/8] mm: page_alloc: add a reserved THP allocation primitive
* [RFC PATCH 4/8] mm: add reserved THP quota helpers
* [RFC PATCH 5/8] mm: add reserved THP vma flag
* [RFC PATCH 6/8] mm: maintain reserved THP quota across VMA changes
* [RFC PATCH 7/8] mm: support reserved THP VMAs in anonymous faults
* [RFC PATCH 8/8] mm: add MADV_RESERVED_THP range policy

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/48c38717-31b4-40a6-88aa-1b581e1fd93b

***

kernel build error

tree:      linux-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base:      3d5670d672ae08b8c534b7beed6f57c8b44e7b43
arch:      amd64
compiler:  Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
config:    https://ci.syzbot.org/builds/d4df29e3-76c2-4d82-b0b4-097beb267ffb/config

ld.lld: error: undefined symbol: reserved_thp_uncharge

***

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: [email protected]

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at [email protected].

To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).

The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.

The email will later be sent to:
[[email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]]

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

If the report is a false positive, reply with
#syz invalid