syzbot


INFO: task hung in kvm_mmu_pre_destroy_vm (4)

Status: upstream: reported syz repro on 2022/02/05 19:19
Reported-by: syzbot+b5682890261cb6ae9636@syzkaller.appspotmail.com
First crash: 863d, last: 484d
Fix bisection: failed (error log, bisect log)
  
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.14 INFO: task hung in kvm_mmu_pre_destroy_vm (2) 1 1471d 1471d 0/1 auto-closed as invalid on 2020/10/05 15:28
linux-4.14 INFO: task hung in kvm_mmu_pre_destroy_vm 3 1630d 1665d 0/1 auto-closed as invalid on 2020/04/30 03:32
linux-4.14 INFO: task hung in kvm_mmu_pre_destroy_vm (3) 5 1166d 1323d 0/1 auto-closed as invalid on 2021/08/07 02:23
upstream INFO: task hung in kvm_mmu_pre_destroy_vm kvm 1 359d 359d 0/27 auto-obsoleted due to no activity on 2023/09/22 14:35
Last patch testing requests (2)
Created Duration User Patch Repo Result
2022/11/11 15:30 9m retest repro linux-4.14.y report log
2022/11/11 14:30 9m retest repro linux-4.14.y report log

Sample crash report:
Bluetooth: hci3 command 0x0406 tx timeout
Bluetooth: hci5 command 0x0406 tx timeout
Bluetooth: hci4 command 0x0406 tx timeout
Bluetooth: hci1 command 0x0406 tx timeout
Bluetooth: hci0 command 0x0406 tx timeout
INFO: task syz-executor.1:32257 blocked for more than 140 seconds.
      Not tainted 4.14.276-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.1  D28912 32257   8043 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2811 [inline]
 __schedule+0x88b/0x1de0 kernel/sched/core.c:3387
 schedule+0x8d/0x1b0 kernel/sched/core.c:3431
 schedule_timeout+0x80a/0xe90 kernel/time/timer.c:1724
 do_wait_for_common kernel/sched/completion.c:91 [inline]
 __wait_for_common kernel/sched/completion.c:112 [inline]
 wait_for_common+0x272/0x430 kernel/sched/completion.c:123
 kthread_stop+0xce/0x640 kernel/kthread.c:555
 kvm_mmu_pre_destroy_vm+0x41/0x50 arch/x86/kvm/mmu.c:5912
 kvm_destroy_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:781 [inline]
 kvm_put_kvm+0x30a/0xab0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:819
 kvm_vm_release+0x3f/0x50 arch/x86/kvm/../../../virt/kvm/kvm_main.c:830
 __fput+0x25f/0x7a0 fs/file_table.c:210
 task_work_run+0x11f/0x190 kernel/task_work.c:113
 tracehook_notify_resume include/linux/tracehook.h:191 [inline]
 exit_to_usermode_loop+0x1ad/0x200 arch/x86/entry/common.c:164
 prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline]
 syscall_return_slowpath arch/x86/entry/common.c:270 [inline]
 do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297
 entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7fcf9ee0ed2b
RSP: 002b:00007ffe15e592a0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 000000000000000b RCX: 00007fcf9ee0ed2b
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 000000000000000a
RBP: 00007fcf9ef70960 R08: 0000000000000000 R09: 00007fcf9ef73760
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000020e37
R13: 00007fcf9ef739a8 R14: 00007fcf9ef6f100 R15: 0000000000000002

Showing all locks held in the system:
1 lock held by khungtaskd/1532:
 #0:  (tasklist_lock){.+.+}, at: [<ffffffff8702578c>] debug_show_all_locks+0x7c/0x21a kernel/locking/lockdep.c:4548
1 lock held by in:imklog/7716:
 #0:  (&f->f_pos_lock){+.+.}, at: [<ffffffff818d692b>] __fdget_pos+0x1fb/0x2b0 fs/file.c:819

=============================================

NMI backtrace for cpu 0
CPU: 0 PID: 1532 Comm: khungtaskd Not tainted 4.14.276-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x1b2/0x281 lib/dump_stack.c:58
 nmi_cpu_backtrace.cold+0x57/0x93 lib/nmi_backtrace.c:101
 nmi_trigger_cpumask_backtrace+0x13a/0x180 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:140 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:195 [inline]
 watchdog+0x5b9/0xb40 kernel/hung_task.c:274
 kthread+0x30d/0x420 kernel/kthread.c:232
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 7717 Comm: rs:main Q:Reg Not tainted 4.14.276-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880a5894500 task.stack: ffff888092200000
RIP: 0010:queue_lock kernel/futex.c:2343 [inline]
RIP: 0010:futex_wait_setup+0xf9/0x260 kernel/futex.c:2792
RSP: 0018:ffff8880922079f0 EFLAGS: 00000202
RAX: ffffc90000c74a00 RBX: ffff888092207af0 RCX: 000000002d6afbba
RDX: 00000000000001ff RSI: 0000000000000000 RDI: 0000000000000200
RBP: ffffed1012440f5e R08: 0000000000000000 R09: 0000000000000000
R10: 1ffff11012440ff9 R11: 0000000000000000 R12: 000055d4f822c28c
R13: ffff888092207a48 R14: ffff888092207bb8 R15: ffffc90000c74a00
FS:  00007f4c92199700(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdebb56f010 CR3: 00000000ab1c2000 CR4: 00000000003426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 futex_wait+0x199/0x5a0 kernel/futex.c:2850
 do_futex+0x1d8/0x1570 kernel/futex.c:3906
 SYSC_futex kernel/futex.c:3966 [inline]
 SyS_futex+0x1da/0x290 kernel/futex.c:3934
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f4c94bda17f
RSP: 002b:00007f4c92198c70 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f4c94bda17f
RDX: 00000000000004af RSI: 0000000000000080 RDI: 000055d4f822c28c
RBP: 000055d4f822c288 R08: 000055d4f822c000 R09: 0000000000000257
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f4c92198cd0
R13: 0000000000000000 R14: 000055d4f7fd3290 R15: 0000000000000000
Code: c1 ed 03 48 01 c5 eb 10 e8 45 3b 09 00 f6 44 24 14 01 0f 85 27 01 00 00 e8 35 3b 09 00 4c 89 f7 e8 4d bf ff ff 49 89 c7 f0 ff 00 <4c> 8d 40 08 48 8b 44 24 08 80 38 00 0f 85 14 01 00 00 48 8b 04 
----------------
Code disassembly (best guess):
   0:	c1 ed 03             	shr    $0x3,%ebp
   3:	48 01 c5             	add    %rax,%rbp
   6:	eb 10                	jmp    0x18
   8:	e8 45 3b 09 00       	callq  0x93b52
   d:	f6 44 24 14 01       	testb  $0x1,0x14(%rsp)
  12:	0f 85 27 01 00 00    	jne    0x13f
  18:	e8 35 3b 09 00       	callq  0x93b52
  1d:	4c 89 f7             	mov    %r14,%rdi
  20:	e8 4d bf ff ff       	callq  0xffffbf72
  25:	49 89 c7             	mov    %rax,%r15
  28:	f0 ff 00             	lock incl (%rax)
* 2b:	4c 8d 40 08          	lea    0x8(%rax),%r8 <-- trapping instruction
  2f:	48 8b 44 24 08       	mov    0x8(%rsp),%rax
  34:	80 38 00             	cmpb   $0x0,(%rax)
  37:	0f 85 14 01 00 00    	jne    0x151
  3d:	48                   	rex.W
  3e:	8b                   	.byte 0x8b
  3f:	04                   	.byte 0x4

Crashes (8):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/04/24 22:00 linux-4.14.y 15a1c6b6f516 131df97d .config console log report syz ci2-linux-4-14 INFO: task hung in kvm_mmu_pre_destroy_vm
2022/02/05 19:19 linux-4.14.y b86ee2b7ae42 a7dab638 .config console log report syz ci2-linux-4-14 INFO: task hung in kvm_mmu_pre_destroy_vm
2023/02/19 16:35 linux-4.14.y a8ad60f2af58 bcdf85f8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in kvm_mmu_pre_destroy_vm
2023/02/12 19:21 linux-4.14.y a8ad60f2af58 93e26d60 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in kvm_mmu_pre_destroy_vm
2022/07/30 14:39 linux-4.14.y b641242202ed fef302b1 .config console log report info ci2-linux-4-14 INFO: task hung in kvm_mmu_pre_destroy_vm
2022/03/12 02:36 linux-4.14.y af48f51cb593 9e8eaa75 .config console log report info ci2-linux-4-14 INFO: task hung in kvm_mmu_pre_destroy_vm
2022/02/26 04:06 linux-4.14.y fa33f9094f36 45a13a73 .config console log report info ci2-linux-4-14 INFO: task hung in kvm_mmu_pre_destroy_vm
2022/02/19 18:27 linux-4.14.y a35d65bedfbc 3cd800e4 .config console log report info ci2-linux-4-14 INFO: task hung in kvm_mmu_pre_destroy_vm
* Struck through repros no longer work on HEAD.