Hello, syzbot found the following issue on: HEAD commit: ca39c4daa6f7 Add linux-next specific files for 20221216 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=1182429d880000 kernel config: https://syzkaller.appspot.com/x/.config?x=9f0bce83c86de334 dashboard link: https://syzkaller.appspot.com/bug?extid=1e164be619b690a43d79 compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/3cbf8a8f223d/disk-ca39c4da.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/f104cf6ddf80/vmlinux-ca39c4da.xz kernel image: https://storage.googleapis.com/syzbot-assets/6ba8b49536b5/bzImage-ca39c4da.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+1e164be619b690a43d79@xxxxxxxxxxxxxxxxxxxxxxxxx INFO: trying to register non-static key. The code is fine but needs lockdep annotation, or maybe you didn't initialize this object before use? turning off the locking correctness validator. CPU: 0 PID: 20857 Comm: syz-executor.5 Not tainted 6.1.0-next-20221216-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd1/0x138 lib/dump_stack.c:106 assign_lock_key kernel/locking/lockdep.c:981 [inline] register_lock_class+0xf1b/0x1120 kernel/locking/lockdep.c:1294 __lock_acquire+0x109/0x56d0 kernel/locking/lockdep.c:4934 lock_acquire.part.0+0x11a/0x350 kernel/locking/lockdep.c:5668 __timer_delete_sync+0x5d/0x1c0 kernel/time/timer.c:1555 del_timer_sync include/linux/timer.h:200 [inline] cleanup_srcu_struct kernel/rcu/srcutree.c:611 [inline] cleanup_srcu_struct+0x112/0x3e0 kernel/rcu/srcutree.c:599 kvm_destroy_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:1325 [inline] kvm_put_kvm+0x884/0xb80 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1352 kvm_vm_release+0x43/0x50 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1375 __fput+0x27c/0xa90 fs/file_table.c:320 task_work_run+0x16f/0x270 kernel/task_work.c:179 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline] exit_to_user_mode_loop kernel/entry/common.c:171 [inline] exit_to_user_mode_prepare+0x23c/0x250 kernel/entry/common.c:203 __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline] syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:296 do_syscall_64+0x46/0xb0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f1a7ae3df8b Code: 0f 05 48 3d 00 f0 ff ff 77 45 c3 0f 1f 40 00 48 83 ec 18 89 7c 24 0c e8 63 fc ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 89 44 24 0c e8 a1 fc ff ff 8b 44 RSP: 002b:00007fff9d5d14e0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003 RAX: 0000000000000000 RBX: 0000000000000005 RCX: 00007f1a7ae3df8b RDX: 0000000000000000 RSI: 0000001b32320ef8 RDI: 0000000000000004 RBP: 00007f1a7afad980 R08: 0000000000000000 R09: 000000008acd30fc R10: 0000000000000000 R11: 0000000000000293 R12: 000000000011376f R13: 00007fff9d5d15e0 R14: 00007f1a7afac050 R15: 0000000000000032 </TASK> ------------[ cut here ]------------ WARNING: CPU: 1 PID: 20857 at kernel/workqueue.c:3066 __flush_work+0x90a/0xaf0 kernel/workqueue.c:3066 Modules linked in: CPU: 1 PID: 20857 Comm: syz-executor.5 Not tainted 6.1.0-next-20221216-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 RIP: 0010:__flush_work+0x90a/0xaf0 kernel/workqueue.c:3066 Code: 00 48 c7 c6 2f 7b 52 81 48 c7 c7 c0 28 79 8c e8 1c 7c 11 00 e9 ab fc ff ff e8 12 d7 2e 00 0f 0b e9 9f fc ff ff e8 06 d7 2e 00 <0f> 0b 45 31 ed e9 90 fc ff ff e8 77 e6 7c 00 e9 7a fb ff ff e8 ed RSP: 0018:ffffc900038afb60 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffffe8ffffcd0620 RCX: 0000000000000000 RDX: ffff888020d38000 RSI: ffffffff81527b6a RDI: 0000000000000001 RBP: ffffc900038afcf8 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000001 R11: 3e4b5341542f3c20 R12: ffffc9000393b478 R13: 0000000000000001 R14: fffffbfff1ce6138 R15: ffffe8ffffcd0638 FS: 0000555555edb400(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000200e9000 CR3: 00000000297ac000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> cleanup_srcu_struct kernel/rcu/srcutree.c:612 [inline] cleanup_srcu_struct+0x11e/0x3e0 kernel/rcu/srcutree.c:599 kvm_destroy_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:1325 [inline] kvm_put_kvm+0x884/0xb80 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1352 kvm_vm_release+0x43/0x50 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1375 __fput+0x27c/0xa90 fs/file_table.c:320 task_work_run+0x16f/0x270 kernel/task_work.c:179 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline] exit_to_user_mode_loop kernel/entry/common.c:171 [inline] exit_to_user_mode_prepare+0x23c/0x250 kernel/entry/common.c:203 __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline] syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:296 do_syscall_64+0x46/0xb0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f1a7ae3df8b Code: 0f 05 48 3d 00 f0 ff ff 77 45 c3 0f 1f 40 00 48 83 ec 18 89 7c 24 0c e8 63 fc ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 89 44 24 0c e8 a1 fc ff ff 8b 44 RSP: 002b:00007fff9d5d14e0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003 RAX: 0000000000000000 RBX: 0000000000000005 RCX: 00007f1a7ae3df8b RDX: 0000000000000000 RSI: 0000001b32320ef8 RDI: 0000000000000004 RBP: 00007f1a7afad980 R08: 0000000000000000 R09: 000000008acd30fc R10: 0000000000000000 R11: 0000000000000293 R12: 000000000011376f R13: 00007fff9d5d15e0 R14: 00007f1a7afac050 R15: 0000000000000032 </TASK> --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@xxxxxxxxxxxxxxxx. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
