[moderation/CI] Re: Fix incorrect access of hugetlb pte entries

syzbot ci has tested the following series

[v3] Fix incorrect access of hugetlb pte entries
https://lore.kernel.org/all/[email protected]
* [PATCH v3 1/6] arm64: make huge_ptep_get handled unaligned addresses
* [PATCH v3 2/6] mm/rmap: use huge_ptep_get() in try_to_unmap_one()
* [PATCH v3 3/6] mm/rmap: use huge_ptep_get() in try_to_migrate_one()
* [PATCH v3 4/6] mm/migrate: use huge_ptep_get() in remove_migration_pte()
* [PATCH v3 5/6] mm/page_vma_mapped: use huge_ptep_get() for hugetlb
* [PATCH v3 6/6] mm/mprotect: use huge_ptep_get() for hugetlb

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/ff6e67cd-e960-43ad-ab95-8bde17ac4f81

***

kernel build error

tree:      mm-new
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base:      6476418cb871288d93c0241d94793c181b61d033
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/f80d76c3-a64e-4cf4-9c67-807616ca426e/config

mm/mprotect.c:711:10: error: use of undeclared identifier 'EACCESS'

***

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