[moderation/CI] Re: KVM: s390: Introduce arm64 KVM

syzbot ci has tested the following series

[v6] KVM: s390: Introduce arm64 KVM
https://lore.kernel.org/all/[email protected]
* [PATCH v6 01/33] vfio: Use file-based reference counting for KVM
* [PATCH v6 02/33] KVM: Make device name configurable
* [PATCH v6 03/33] KVM: Allow KVM implementations to switch off MMIO independent of Kconfig
* [PATCH v6 04/33] arm64: Use proper include variant
* [PATCH v6 05/33] arm64: ptrace: Use constants for compat register numbers
* [PATCH v6 06/33] arm64: sysreg: Convert SPSR_ELx to automatic register generation
* [PATCH v6 07/33] KVM: arm64: Access elements of vcpu_gp_regs individually
* [PATCH v6 08/33] KVM: arm64: Use accessor functions for core regs
* [PATCH v6 09/33] arm64: Prepare sharing arm64 headers with s390
* [PATCH v6 10/33] arm64: Share arm64 headers with s390
* [PATCH v6 11/33] KVM: arm64: Share arm64 code with s390
* [PATCH v6 12/33] KVM: s390: Extract gmap tracing to a separate header
* [PATCH v6 13/33] KVM: s390: Prepare include guards for a new location
* [PATCH v6 14/33] KVM: s390: Rename kvm-s390.{c,h} to s390.{c,h}
* [PATCH v6 15/33] KVM: s390: Move kvm_host definitions to kvm_host_s390
* [PATCH v6 16/33] KVM: s390: Move s390 kvm code into a subdirectory
* [PATCH v6 17/33] KVM: s390: Move PGM code definitions to asm/kvm_host.h
* [PATCH v6 18/33] KVM: s390: Prepare gmap for a second KVM implementation
* [PATCH v6 19/33] KVM: s390: gmap: Make storage keys optional
* [PATCH v6 20/33] KVM: s390: gmap: Make CMMA optional
* [PATCH v6 21/33] KVM: s390: gmap: Make prefix handling optional
* [PATCH v6 22/33] KVM: s390: Prepare KVM/s390 for a second KVM module
* [PATCH v6 23/33] s390: Use arm64 headers
* [PATCH v6 24/33] KVM: s390: Use arm64 code
* [PATCH v6 25/33] s390: Introduce Start Arm Execution instruction
* [PATCH v6 26/33] KVM: s390: arm64: Introduce host definitions
* [PATCH v6 27/33] s390/hwcaps: Report SAE support as hwcap
* [PATCH v6 28/33] KVM: s390: Add basic arm64 kvm module
* [PATCH v6 29/33] KVM: s390: arm64: Implement required functions
* [PATCH v6 30/33] KVM: s390: arm64: Implement vm/vcpu create destroy.
* [PATCH v6 31/33] KVM: s390: arm64: Implement vCPU IOCTLs
* [PATCH v6 32/33] KVM: s390: arm64: Implement basic page fault handler
* [PATCH v6 33/33] KVM: s390: arm64: Enable KVM_ARM64 config and Kbuild

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/f8f86d18-d51e-46a4-9c78-a6c3b3725817

***

kernel build error

tree:      linux-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base:      5e6de6a2b522f659defacb1551d0465ba6ce13cf
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/2ede6171-aff4-442a-95cd-d85847a0fef1/config

drivers/vfio/vfio_main.c:1549:29: error: incompatible pointer types passing 'struct file *' to parameter of type 'struct kvm *' [-Wincompatible-pointer-types]

***

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 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 [email protected].
- 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]]

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

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