On Thu, Mar 16, 2023, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: ee3f96b16468 Merge tag 'nfsd-6.3-1' of git://git.kernel.or.. > git tree: upstream > console+strace: https://syzkaller.appspot.com/x/log.txt?x=11622f64c80000 > kernel config: https://syzkaller.appspot.com/x/.config?x=cab35c936731a347 > dashboard link: https://syzkaller.appspot.com/bug?extid=8accb43ddc6bd1f5713a > compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15bd61acc80000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17402eb0c80000 > > Downloadable assets: > disk image: https://storage.googleapis.com/syzbot-assets/a7ac3e540d6d/disk-ee3f96b1.raw.xz > vmlinux: https://storage.googleapis.com/syzbot-assets/604b5042d73d/vmlinux-ee3f96b1.xz > kernel image: https://storage.googleapis.com/syzbot-assets/5a6d400b42b5/bzImage-ee3f96b1.xz > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+8accb43ddc6bd1f5713a@xxxxxxxxxxxxxxxxxxxxxxxxx > > kvm_intel: KVM_SET_TSS_ADDR needs to be called before running vCPU > kvm_intel: set kvm_intel.dump_invalid_vmcs=1 to dump internal KVM state. > ------------[ cut here ]------------ > WARNING: CPU: 0 PID: 5082 at arch/x86/kvm/x86.c:11060 kvm_arch_vcpu_ioctl_run+0x2464/0x2af0 arch/x86/kvm/x86.c:11060 > Modules linked in: > CPU: 0 PID: 5082 Comm: syz-executor178 Not tainted 6.2.0-syzkaller-13115-gee3f96b16468 #0 > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023 > RIP: 0010:kvm_arch_vcpu_ioctl_run+0x2464/0x2af0 arch/x86/kvm/x86.c:11060 Same thing reported by another syzkaller instance, I'll post fixes in the not too distant future. https://lore.kernel.org/all/ZBNrWZQhMX8AHzWM@xxxxxxxxxx
