[moderation/CI] Re: KVM: Use atomic SRCU for gfn-to-pfn cache, reinstate guest mode for x86 nesting

[moderation/CI] Re: KVM: Use atomic SRCU for gfn-to-pfn cache, reinstate guest mode for x86 nesting

[syzbot ci]

syzbot ci has tested the following series

[v1] KVM: Use atomic SRCU for gfn-to-pfn cache, reinstate guest mode for x86 nesting
https://lore.kernel.org/all/20260920211920.928306-1-dwmw2@infradead.org
* [PATCH 01/17] KVM: pfncache: Use atomic SRCU for readers instead of a rwlock
* [PATCH 02/17] KVM: x86/xen: Extract delivery of event to vCPU into a separate helper
* [PATCH 03/17] KVM: x86/xen: Explicitly tag "shared info" page as never being dirty tracked
* [PATCH 04/17] KVM: x86/xen: Don't dirty track "vCPU info" page
* [PATCH 05/17] KVM: x86: Request the guest TLB flush from record_steal_time()
* [PATCH 06/17] KVM: x86: Use gfn_to_pfn_cache for steal time / preempted status
* [PATCH 07/17] KVM: pfncache: Add guest-mode pinning (GUEST_USES_PFN successor)
* [PATCH 08/17] KVM: pfncache: Return -EAGAIN for a lookup which hits an invalid memslot
* [PATCH 09/17] KVM: x86: Post KVM_REQ_GET_NESTED_STATE_PAGES on memslot updates
* [PATCH 10/17] KVM: nVMX: Implement cache for L1 MSR bitmap
* [PATCH 11/17] KVM: nVMX: Use pinned pfncache for L1 APIC virtualization pages
* [PATCH 12/17] KVM: selftests: Add nested VMX APIC cache invalidation test
* [PATCH 13/17] KVM: x86: Move nested GPC lock helpers to x86.h as kvm_gpc_lock_page()
* [PATCH 14/17] KVM: nSVM: Use a gfn_to_pfn_cache for the vmcb12 page
* [PATCH 15/17] KVM: nSVM: Cache L1's MSR permissions map pages
* [PATCH 16/17] KVM: nSVM: Cache L1's IO permissions map pages
* [PATCH 17/17] KVM: selftests: Add nested transition benchmark

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/b30937af-ed9b-4623-9756-ab12f5e10d48

***

kernel build error

tree:      kvm-next
URL:       https://kernel.googlesource.com/pub/scm/virt/kvm/kvm/
base:      d4b7fb647204f0c81dfeae2d1a708e4d858e0c94
arch:      amd64
compiler:  Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config:    https://ci.syzbot.org/builds/9ea66f31-e98a-4e31-b4bf-071f60d487b9/config

./include/linux/srcu.h:640:7: error: call to undeclared function 'srcu_read_unlock_atomic'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
./include/linux/srcu.h:639:17: error: call to undeclared function 'srcu_read_lock_atomic'; 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: syzbot@syzkaller.appspotmail.com

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.

To test a fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.

Notes:
- The patch will be applied on top of the tested series (as an
  incremental fix).
- To test a new version of the whole series, please send it directly
  to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.

The email will later be sent to:
[bigeasy@linutronix.de boqun.feng@gmail.com clrkwllms@kernel.org dmatlack@google.com dwmw2@infradead.org dwmw@amazon.co.uk fgriffo@amazon.co.uk jgg@ziepe.ca jiangshanlai@gmail.com joelagnelf@nvidia.com josh@joshtriplett.org kalyazin@amazon.com keirf@google.com kunwu.chan@gmail.com kunwu.chan@linux.dev kvm@vger.kernel.org linux-kernel@vger.kernel.org linux-kselftest@vger.kernel.org linux-rt-devel@lists.linux.dev mathieu.desnoyers@efficios.com mhocko@suse.com neeraj.upadhyay@kernel.org nh-open-source@amazon.com paul@xen.org paulmck@kernel.org pbonzini@redhat.com qiang.zhang@linux.dev rcu@vger.kernel.org rostedt@goodmis.org sashiko-bot@kernel.org seanjc@google.com stollmc@amazon.com syzbot@syzkaller.appspotmail.com vkuznets@redhat.com]

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

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