[moderation/CI] Re: mm, bpf: BPF-MM, BPF-THP

[syzbot ci]

syzbot ci has tested the following series

[v10] mm, bpf: BPF-MM, BPF-THP
https://lore.kernel.org/all/20251015141716....@gmail.com
* [RFC PATCH v10 mm-new 1/9] mm: thp: remove vm_flags parameter from khugepaged_enter_vma()
* [RFC PATCH v10 mm-new 2/9] mm: thp: remove vm_flags parameter from thp_vma_allowable_order()
* [RFC PATCH v10 mm-new 3/9] mm: thp: add support for BPF based THP order selection
* [RFC PATCH v10 mm-new 4/9] mm: thp: decouple THP allocation between swap and page fault paths
* [RFC PATCH v10 mm-new 5/9] mm: thp: enable THP allocation exclusively through khugepaged
* [RFC PATCH v10 mm-new 6/9] bpf: mark mm->owner as __safe_rcu_or_null
* [RFC PATCH v10 mm-new 7/9] bpf: mark vma->vm_mm as __safe_trusted_or_null
* [RFC PATCH v10 mm-new 8/9] selftests/bpf: add a simple BPF based THP policy
* [RFC PATCH v10 mm-new 9/9] Documentation: add BPF-based THP policy management

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/a8a425e8-ff46-4bac-bf93-1ee0aad0c36a

***

kernel build error

tree: bpf-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base: 56b4d162392dda2365fbc1f482184a24b489d07d
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/7b9d324c-f37b-4dfb-bbb3-f6ff6b11b136/config

kernel/fork.c:1133:2: error: call to undeclared function 'bpf_thp_exit_mm'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]

***

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:
[21c...@gmail.com ak...@linux-foundation.org amer...@gmail.com and...@kernel.org a...@kernel.org baoli...@linux.alibaba.com b...@vger.kernel.org cor...@lwn.net dan...@iogearbox.net da...@redhat.com dev....@arm.com gutierr...@huawei-partners.com han...@cmpxchg.org lance...@linux.dev laoar...@gmail.com liam.h...@oracle.com linu...@vger.kernel.org linux-...@vger.kernel.org linu...@kvack.org lorenzo...@oracle.com npa...@redhat.com rdu...@infradead.org rien...@google.com ryan.r...@arm.com shakee...@linux.dev shy8...@gmail.com t...@kernel.org usamaa...@gmail.com wi...@infradead.org z...@nvidia.com]

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