From: syzbot ci <syzbot+ci970088ae3d7f589e@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: KVM: s390: Introduce arm64 KVM
Date: Wed, 12 Aug 2026 11:43:49 -0700 [thread overview]
Message-ID: <6a7cbee5.ed659fcc.23056a.0086.GAE@google.com> (raw)
syzbot ci has tested the following series
[v6] KVM: s390: Introduce arm64 KVM
https://lore.kernel.org/all/20260812153631.3376090-1-seiden@linux.ibm.com
* [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: 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:
[agordeev@linux.ibm.com arnd@arndb.de borntraeger@linux.ibm.com brueckner@linux.ibm.com catalin.marinas@arm.com david@kernel.org frankja@linux.ibm.com fritz@linux.ibm.com ggala@linux.ibm.com gor@linux.ibm.com gra@linux.ibm.com hari55@linux.ibm.com hca@linux.ibm.com iii@linux.ibm.com imbrenda@linux.ibm.com joey.gouly@arm.com kvm@vger.kernel.org kvmarm@lists.linux.dev linux-arm-kernel@lists.infradead.org linux-kernel@vger.kernel.org linux-s390@vger.kernel.org maz@kernel.org nrb@linux.ibm.com oss@nina.schoetterlglausch.eu oupton@kernel.org pbonzini@redhat.com seanjc@google.com seiden@linux.ibm.com suzuki.poulose@arm.com svens@linux.ibm.com tabba@google.com ulrich.weigand@de.ibm.com will@kernel.org yuzenghui@huawei.com]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
reply other threads:[~2026-08-12 18:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a7cbee5.ed659fcc.23056a.0086.GAE@google.com \
--to=syzbot+ci970088ae3d7f589e@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).