ci2 starts bisection 2023-06-18 19:09:14.845158215 +0000 UTC m=+250378.037954962 bisecting fixing commit since 9d6bde853685609a631871d7c12be94fdf8d912e building syzkaller on 3bb7af1def6b7b99e4c1c9573162eb41b5893cd3 ensuring issue is reproducible on original commit 9d6bde853685609a631871d7c12be94fdf8d912e testing commit 9d6bde853685609a631871d7c12be94fdf8d912e gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: e5103f778a1232cba0f5b4fe5daf82f641016dae735b65b1ced95c5ca93c1a77 all runs: crashed: WARNING: suspicious RCU usage in kvm_vcpu_gfn_to_memslot testing current HEAD 471e639e59d128f4bf58000a118b2ceca3893f98 testing commit 471e639e59d128f4bf58000a118b2ceca3893f98 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 34c6f061a43a184998bf5a9a52ae40377cebbf655a12b2afe77a05e87b7c3fa4 all runs: crashed: WARNING: suspicious RCU usage in kvm_vcpu_gfn_to_memslot crash still not fixed/happens on the oldest tested release revisions tested: 2, total time: 33m53.737474041s (build: 26m41.640844357s, test: 6m11.580387005s) crash still not fixed on HEAD or HEAD had kernel test errors commit msg: Linux 5.15.117 crash: WARNING: suspicious RCU usage in kvm_vcpu_gfn_to_memslot L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. ============================= WARNING: suspicious RCU usage 5.15.117-syzkaller #0 Not tainted ----------------------------- include/linux/kvm_host.h:878 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz-executor.0/3967: #0: ffff88807c8300c8 (&vcpu->mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x198/0xb50 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3840 stack backtrace: CPU: 0 PID: 3967 Comm: syz-executor.0 Not tainted 5.15.117-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x57/0x7d lib/dump_stack.c:106 __kvm_memslots include/linux/kvm_host.h:878 [inline] __kvm_memslots include/linux/kvm_host.h:875 [inline] kvm_vcpu_memslots include/linux/kvm_host.h:892 [inline] kvm_vcpu_gfn_to_memslot+0x3ee/0x540 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2140 kvm_vcpu_unmap+0x39/0x90 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2755 nested_vmx_vmexit+0x74c/0x3400 arch/x86/kvm/vmx/nested.c:4662 vmx_leave_nested+0x7c/0xa0 arch/x86/kvm/vmx/nested.c:6322 kvm_leave_nested arch/x86/kvm/x86.c:618 [inline] kvm_vcpu_ioctl_x86_set_vcpu_events+0x7cb/0xe80 arch/x86/kvm/x86.c:4793 kvm_arch_vcpu_ioctl+0x545/0x2db0 arch/x86/kvm/x86.c:5278 kvm_vcpu_ioctl+0x747/0xb50 arch/x86/kvm/../../../virt/kvm/kvm_main.c:4019 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl fs/ioctl.c:860 [inline] __x64_sys_ioctl+0x11f/0x190 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f77d8ca0169 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f77d8012168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f77d8dbff80 RCX: 00007f77d8ca0169 RDX: 00000000200000c0 RSI: 000000004040aea0 RDI: 0000000000000005 RBP: 00007f77d8cfbca1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe4773bd8f R14: 00007f77d8012300 R15: 0000000000022000