[moderation/CI] Re: hugetlb: Use PAGE granularity index in exported i/f and adopt the common read_iter

syzbot ci has tested the following series

[v2] hugetlb: Use PAGE granularity index in exported i/f and adopt the common read_iter
https://lore.kernel.org/all/[email protected]
* [PATCH v2 01/11] mm/memory-failure: make is_raw_hwpoison_page_in_hugepage() general purpose
* [PATCH v2 02/11] mm: factor out adjust_range_hwpoison() from hugetlbfs
* [PATCH v2 03/11] mm/filemap: add hwpoison handling to filemap_read()
* [PATCH v2 04/11] hugetlbfs,filemap: replace hugetlbfs_read_iter() with generic_file_read_iter()
* [PATCH v2 05/11] hugetlb: Convert the vmf->pgoff to PAGE_SIZE granularity
* [PATCH v2 06/11] hugetlb: make hugetlb_fault_mutex_hash() to take PAGE_SIZE index
* [PATCH v2 07/11] hugetlb: replace filemap_lock_hugetlb_folio with filemap_lock_folio
* [PATCH v2 08/11] hugetlb: make hugetlb_add_to_page_cache() to take PAGE_SIZE granularity index
* [PATCH v2 09/11] hugetlb: remove the hugetlb_linear_page_index() helper
* [PATCH v2 10/11] hugetlb: drop vma_hugecache_offset() in favor of linear_page_index()
* [PATCH v2 11/11] hugetlb: make hugetlb_[un]reserve_pages() to take PAGE granularity index

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/46af513c-ee7e-4b9d-9710-b8534d0c03bc

***

kernel build error

tree:      mm-new
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base:      f2737dc40d2ef3e9f3f9395d61f53f6668306a71
arch:      amd64
compiler:  Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config:    https://ci.syzbot.org/builds/3c2981fa-3715-41da-8819-23a981a31c0d/config

ld.lld: error: undefined symbol: is_raw_hwpoison_page_in_folio

***

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]]

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

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