[moderation/CI] Re: Introduce meminspect

syzbot ci has tested the following series

[v3] Introduce meminspect
https://lore.kernel.org/all/[email protected]
* [PATCH v3 01/26] kernel: Introduce meminspect
* [PATCH v3 02/26] init/version: Annotate static information into meminspect
* [PATCH v3 03/26] mm/percpu: Annotate static information into meminspect
* [PATCH v3 04/26] cpu: Annotate static information into meminspect
* [PATCH v3 05/26] genirq/irqdesc: Annotate static information into meminspect
* [PATCH v3 06/26] timers: Annotate static information into meminspect
* [PATCH v3 07/26] timekeeping: Register tk_data into meminspect
* [PATCH v3 08/26] kernel/fork: Annotate static information into meminspect
* [PATCH v3 09/26] mm/page_alloc: Annotate static information into meminspect
* [PATCH v3 10/26] mm/show_mem: Annotate static information into meminspect
* [PATCH v3 11/26] mm/swapfile: Annotate static information into meminspect
* [PATCH v3 12/26] kernel/vmcore_info: Register dynamic information into meminspect
* [PATCH v3 13/26] kernel/configs: Register dynamic information into meminspect
* [PATCH v3 14/26] mm/init-mm: Annotate static information into meminspect
* [PATCH v3 15/26] panic: Annotate static information into meminspect
* [PATCH v3 16/26] kallsyms: Annotate static information into meminspect
* [PATCH v3 17/26] mm/mm_init: Annotate static information into meminspect
* [PATCH v3 18/26] sched/core: Annotate runqueues into meminspect
* [PATCH v3 19/26] mm/numa: Register node data information into meminspect
* [PATCH v3 20/26] mm/sparse: Register information into meminspect
* [PATCH v3 21/26] printk: Register information into meminspect
* [PATCH v3 22/26] remoteproc: qcom: Move minidump data structures into its own header
* [PATCH v3 23/26] soc: qcom: Add minidump backend driver
* [PATCH v3 24/26] soc: qcom: smem: Add minidump platform device
* [PATCH v3 25/26] dt-bindings: reserved-memory: Add Google Kinfo Pixel reserved memory
* [PATCH v3 26/26] meminspect: Add debug kinfo compatible driver

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/7c1c745b-0789-4516-aa2c-423182a6da3d

***

kernel build error

tree:      mm-new
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base:      302dfbff3e73be2ba5723237c6303244ec27cebb
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/c521c853-b48a-430e-b3d4-94e50203ef8e/config

kernel/configs.c:69:2: error: call to undeclared function 'virt_to_phys'; 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: [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] [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