syzbot


INFO: task hung in hci_dev_close_sync
Status: upstream: reported on 2022/05/03 16:59
Reported-by: syzbot+c56f6371c48cad0420f9@syzkaller.appspotmail.com
First crash: 30d, last: 2h45m

Sample crash report:
INFO: task kworker/u5:0:49 blocked for more than 143 seconds.
      Not tainted 5.18.0-syzkaller-10139-g8291eaafed36 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u5:0    state:D stack:26288 pid:   49 ppid:     2 flags:0x00004000
Workqueue: hci3 hci_power_on
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5116 [inline]
 __schedule+0xa00/0x4b30 kernel/sched/core.c:6431
 schedule+0xd2/0x1f0 kernel/sched/core.c:6503
 schedule_timeout+0x1db/0x2a0 kernel/time/timer.c:1911
 do_wait_for_common kernel/sched/completion.c:85 [inline]
 __wait_for_common+0x378/0x530 kernel/sched/completion.c:106
 __flush_work+0x56c/0xb10 kernel/workqueue.c:3075
 __cancel_work_timer+0x3f9/0x570 kernel/workqueue.c:3162
 hci_dev_close_sync+0x8d/0x1150 net/bluetooth/hci_sync.c:4091
 hci_dev_do_close+0x32/0x70 net/bluetooth/hci_core.c:553
 hci_power_on+0x1c0/0x630 net/bluetooth/hci_core.c:981
 process_one_work+0x996/0x1610 kernel/workqueue.c:2289
 worker_thread+0x665/0x1080 kernel/workqueue.c:2436
 kthread+0x2e9/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:302
 </TASK>
INFO: task syz-executor.3:16879 blocked for more than 143 seconds.
      Not tainted 5.18.0-syzkaller-10139-g8291eaafed36 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3  state:D stack:29168 pid:16879 ppid:     1 flags:0x00000000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5116 [inline]
 __schedule+0xa00/0x4b30 kernel/sched/core.c:6431
 schedule+0xd2/0x1f0 kernel/sched/core.c:6503
 schedule_timeout+0x1db/0x2a0 kernel/time/timer.c:1911
 do_wait_for_common kernel/sched/completion.c:85 [inline]
 __wait_for_common+0x378/0x530 kernel/sched/completion.c:106
 flush_workqueue+0x3ed/0x13a0 kernel/workqueue.c:2861
 hci_dev_open+0xdb/0x300 net/bluetooth/hci_core.c:526
 hci_sock_ioctl+0x62c/0x910 net/bluetooth/hci_sock.c:1027
 sock_do_ioctl+0xcc/0x230 net/socket.c:1169
 sock_ioctl+0x2f1/0x640 net/socket.c:1286
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl fs/ioctl.c:856 [inline]
 __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:856
 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+0x46/0xb0
RIP: 0033:0x7fe5f2a88ec7
RSP: 002b:00007ffd8d09cb78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ffd8d09d238 RCX: 00007fe5f2a88ec7
RDX: 0000000000000003 RSI: 00000000400448c9 RDI: 0000000000000003
RBP: 0000000000000003 R08: 00007fe5f21ff700 R09: 00007fe5f21ff700
R10: 00007fe5f21ff9d0 R11: 0000000000000246 R12: 0000000000000003
R13: 00007ffd8d09ccd0 R14: 00007fe5f2b9c9b8 R15: 000000000000000c
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
1 lock held by khungtaskd/29:
 #0: ffffffff8bd83da0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x53/0x260 kernel/locking/lockdep.c:6491
2 locks held by kworker/u4:2/46:
 #0: ffff888010c74138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff888010c74138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
 #0: ffff888010c74138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1280 [inline]
 #0: ffff888010c74138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:636 [inline]
 #0: ffff888010c74138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:663 [inline]
 #0: ffff888010c74138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x87a/0x1610 kernel/workqueue.c:2260
 #1: ffffc90000d7fda8 ((work_completion)(&(&kfence_timer)->work)){+.+.}-{0:0}, at: process_one_work+0x8ae/0x1610 kernel/workqueue.c:2264
3 locks held by kworker/u5:0/49:
 #0: ffff88801b3bb138 ((wq_completion)hci3){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff88801b3bb138 ((wq_completion)hci3){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
 #0: ffff88801b3bb138 ((wq_completion)hci3){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1280 [inline]
 #0: ffff88801b3bb138 ((wq_completion)hci3){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:636 [inline]
 #0: ffff88801b3bb138 ((wq_completion)hci3){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:663 [inline]
 #0: ffff88801b3bb138 ((wq_completion)hci3){+.+.}-{0:0}, at: process_one_work+0x87a/0x1610 kernel/workqueue.c:2260
 #1: ffffc90000dafda8 ((work_completion)(&hdev->power_on)){+.+.}-{0:0}, at: process_one_work+0x8ae/0x1610 kernel/workqueue.c:2264
 #2: ffff888028d29048 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close+0x2a/0x70 net/bluetooth/hci_core.c:551
2 locks held by getty/3290:
 #0: ffff88801fea9098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:244
 #1: ffffc900013f02e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xcea/0x1230 drivers/tty/n_tty.c:2075

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

NMI backtrace for cpu 0
CPU: 0 PID: 29 Comm: khungtaskd Not tainted 5.18.0-syzkaller-10139-g8291eaafed36 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 nmi_cpu_backtrace.cold+0x47/0x144 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x1e6/0x230 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
 watchdog+0xc22/0xf90 kernel/hung_task.c:378
 kthread+0x2e9/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:302
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 16 Comm: pr/ttyS0 Not tainted 5.18.0-syzkaller-10139-g8291eaafed36 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:io_serial_in+0x83/0xa0 drivers/tty/serial/8250/8250_port.c:461
Code: 19 1a fd 48 8d 7d 40 44 89 e1 48 b8 00 00 00 00 00 fc ff df 48 89 fa d3 e3 48 c1 ea 03 80 3c 02 00 75 16 66 03 5d 40 89 da ec <5b> 0f b6 c0 5d 41 5c c3 e8 30 33 66 fd eb a6 e8 59 33 66 fd eb e3
RSP: 0018:ffffc9000036fac0 EFLAGS: 00000002
RAX: dffffc0000000000 RBX: 00000000000003fd RCX: 0000000000000000
RDX: 00000000000003fd RSI: ffffffff845f876c RDI: ffffffff908d3b40
RBP: ffffffff908d3b00 R08: 0000000000000001 R09: 000000000000001f
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
R13: fffffbfff211a7b3 R14: fffffbfff211a76a R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c0037871d2 CR3: 000000000ba8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 serial_in drivers/tty/serial/8250/8250.h:115 [inline]
 wait_for_xmitr+0x9a/0x210 drivers/tty/serial/8250/8250_port.c:2089
 serial8250_console_putchar+0x1d/0x60 drivers/tty/serial/8250/8250_port.c:3310
 uart_console_write+0x59/0x100 drivers/tty/serial/serial_core.c:1935
 serial8250_console_write+0xa57/0xc30 drivers/tty/serial/8250/8250_port.c:3382
 call_console_driver kernel/printk/printk.c:2075 [inline]
 __console_emit_next_record+0x896/0xa60 kernel/printk/printk.c:2916
 console_emit_next_record kernel/printk/printk.c:3721 [inline]
 printk_kthread_func.cold+0x702/0x73d kernel/printk/printk.c:3837
 kthread+0x2e9/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:302
 </TASK>
----------------
Code disassembly (best guess):
   0:	19 1a                	sbb    %ebx,(%rdx)
   2:	fd                   	std
   3:	48 8d 7d 40          	lea    0x40(%rbp),%rdi
   7:	44 89 e1             	mov    %r12d,%ecx
   a:	48 b8 00 00 00 00 00 	movabs $0xdffffc0000000000,%rax
  11:	fc ff df
  14:	48 89 fa             	mov    %rdi,%rdx
  17:	d3 e3                	shl    %cl,%ebx
  19:	48 c1 ea 03          	shr    $0x3,%rdx
  1d:	80 3c 02 00          	cmpb   $0x0,(%rdx,%rax,1)
  21:	75 16                	jne    0x39
  23:	66 03 5d 40          	add    0x40(%rbp),%bx
  27:	89 da                	mov    %ebx,%edx
  29:	ec                   	in     (%dx),%al
* 2a:	5b                   	pop    %rbx <-- trapping instruction
  2b:	0f b6 c0             	movzbl %al,%eax
  2e:	5d                   	pop    %rbp
  2f:	41 5c                	pop    %r12
  31:	c3                   	retq
  32:	e8 30 33 66 fd       	callq  0xfd663367
  37:	eb a6                	jmp    0xffffffdf
  39:	e8 59 33 66 fd       	callq  0xfd663397
  3e:	eb e3                	jmp    0x23

Crashes (271):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-kasan-gce-selinux-root 2022/05/27 23:22 upstream 8291eaafed36 a46af346 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce-root 2022/05/27 21:10 upstream 8291eaafed36 a46af346 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce 2022/05/27 19:47 upstream 7e284070abe5 116e7a7b .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce 2022/05/27 17:20 upstream 7e284070abe5 116e7a7b .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce 2022/05/27 13:00 upstream 7e284070abe5 116e7a7b .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce-root 2022/05/27 09:57 upstream 7e284070abe5 116e7a7b .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce-selinux-root 2022/05/27 08:38 upstream 7f50d4dfe816 116e7a7b .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce 2022/05/27 06:09 upstream babf0bb978e3 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce-selinux-root 2022/05/27 03:52 upstream 7f50d4dfe816 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce-selinux-root 2022/05/27 02:34 upstream 7f50d4dfe816 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce-root 2022/05/27 01:14 upstream babf0bb978e3 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce-smack-root 2022/05/26 23:22 upstream babf0bb978e3 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce-root 2022/05/26 20:49 upstream babf0bb978e3 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce 2022/05/26 16:44 upstream 7e062cda7d90 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce 2022/05/26 15:15 upstream 7e062cda7d90 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce-selinux-root 2022/05/26 13:16 upstream babf0bb978e3 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce-root 2022/05/26 06:55 upstream 7e062cda7d90 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce-smack-root 2022/05/26 04:35 upstream 7e062cda7d90 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce-selinux-root 2022/05/26 02:55 upstream 7e062cda7d90 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce-smack-root 2022/05/26 01:13 upstream 7e062cda7d90 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce-root 2022/05/26 00:52 upstream 7e062cda7d90 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-kasan-gce-386 2022/05/28 00:40 upstream 8291eaafed36 a46af346 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/27 22:21 linux-next d3fde8ff50ab a46af346 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/27 21:08 linux-next d3fde8ff50ab a46af346 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/27 08:38 linux-next d3fde8ff50ab 116e7a7b .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/27 07:21 linux-next d3fde8ff50ab 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/26 08:12 linux-next b1d84fc09a96 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/25 23:49 linux-next 8cb8311e95e3 3037caa9 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/25 13:49 linux-next 8cb8311e95e3 647c0e27 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/25 12:45 linux-next 8cb8311e95e3 647c0e27 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/25 08:24 linux-next 8cb8311e95e3 647c0e27 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/25 07:19 linux-next 8cb8311e95e3 647c0e27 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/25 00:48 linux-next 09ce5091ff97 647c0e27 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/24 18:20 linux-next 09ce5091ff97 fcfad4ff .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/24 16:16 linux-next 09ce5091ff97 fcfad4ff .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/24 12:14 linux-next 09ce5091ff97 fcfad4ff .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/24 11:06 linux-next 09ce5091ff97 e7f9308d .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/24 10:06 linux-next 09ce5091ff97 e7f9308d .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/24 02:03 linux-next cc63e8e92cb8 e7f9308d .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/24 00:28 linux-next cc63e8e92cb8 e7f9308d .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/23 13:16 linux-next cc63e8e92cb8 4c7657cb .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/23 12:08 linux-next cc63e8e92cb8 4c7657cb .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/23 10:25 linux-next 18ecd30af1a8 4c7657cb .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/22 13:49 linux-next 18ecd30af1a8 7268fa62 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/22 12:12 linux-next 18ecd30af1a8 7268fa62 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/22 11:35 linux-next 18ecd30af1a8 7268fa62 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/22 07:54 linux-next 18ecd30af1a8 7268fa62 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/05/02 23:30 linux-next 9f9b9a2972eb 2df221f6 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/04/29 16:53 linux-next 5469f0c06732 44a5ca63 .config log report info INFO: task hung in hci_dev_close_sync
ci-upstream-linux-next-kasan-gce-root 2022/04/27 07:08 linux-next f02ac5c95dfd 1fa34c1b .config log report info INFO: task hung in hci_dev_close_sync