[moderation/CI] Re: Use generic_file_read_iter() in hugetlbfs

syzbot ci has tested the following series

[v1] Use generic_file_read_iter() in hugetlbfs
https://lore.kernel.org/all/[email protected]
* [PATCH 1/4] hugetlbfs: Set mapping folio order
* [PATCH 2/4] mm: Handle hugetlb correctly in is_page_hwpoison()
* [PATCH 3/4] filemap: add hwpoison handling to filemap_read()
* [PATCH 4/4] hugetlbfs: replace hugetlbfs_read_iter() with generic_file_read_iter()

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/5869d756-5b77-45e0-b5c2-de0fca422e49

***

kernel build error

tree:      mm-new
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base:      dc59e4fea9d83f03bad6bddf3fa2e52491777482
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/074ace85-e34d-4e22-a00b-a735d5f0684e/config

mm/memory-failure.c:1841:44: error: passing 'const struct folio *' to parameter of type 'struct folio *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
mm/memory-failure.c:1846:35: error: passing 'const struct folio *' to parameter of type 'struct folio *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers]

***

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

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

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