syzbot


INFO: task hung in hci_cmd_sync_clear

Status: auto-obsoleted due to no activity on 2022/11/16 14:10
Subsystems: bluetooth
[Documentation on labels]
First crash: 928d, last: 781d
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 INFO: task hung in hci_cmd_sync_clear 1 204d 204d 0/3 auto-obsoleted due to no activity on 2024/06/24 21:55
upstream INFO: task hung in hci_cmd_sync_clear (2) bluetooth 15 196d 601d 0/28 auto-obsoleted due to no activity on 2024/06/23 16:01

Sample crash report:
INFO: task syz-executor.2:18258 blocked for more than 143 seconds.
      Not tainted 6.0.0-rc1-syzkaller-00025-g274a2eebf80c #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2  state:D stack:21752 pid:18258 ppid:     1 flags:0x00004002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5182 [inline]
 __schedule+0x957/0xe20 kernel/sched/core.c:6494
 schedule+0xcb/0x190 kernel/sched/core.c:6570
 schedule_timeout+0xac/0x300 kernel/time/timer.c:1911
 do_wait_for_common+0x3ea/0x560 kernel/sched/completion.c:85
 __wait_for_common kernel/sched/completion.c:106 [inline]
 wait_for_common kernel/sched/completion.c:117 [inline]
 wait_for_completion+0x46/0x60 kernel/sched/completion.c:138
 __flush_work kernel/workqueue.c:3075 [inline]
 __cancel_work_timer+0x585/0x740 kernel/workqueue.c:3162
 hci_cmd_sync_clear+0x2c/0x210 net/bluetooth/hci_sync.c:337
 hci_unregister_dev+0x137/0x460 net/bluetooth/hci_core.c:2676
 vhci_release+0x7f/0xd0 drivers/bluetooth/hci_vhci.c:568
 __fput+0x3b9/0x820 fs/file_table.c:320
 task_work_run+0x146/0x1c0 kernel/task_work.c:177
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0x55e/0x20a0 kernel/exit.c:795
 do_group_exit+0x23b/0x2f0 kernel/exit.c:925
 __do_sys_exit_group kernel/exit.c:936 [inline]
 __se_sys_exit_group kernel/exit.c:934 [inline]
 __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:934
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f8ce5c89279
RSP: 002b:00007ffd00ecf7d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007ffd00ecf980 RCX: 00007f8ce5c89279
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000043
RBP: 0000000000000000 R08: 0000000000000025 R09: 00007ffd00ecf980
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f8ce5ce315a
R13: 000000000000001c R14: 0000000000000003 R15: 00007ffd00ecf9c0
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
 #0: ffffffff8cd20970 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x30/0xd00 kernel/rcu/tasks.h:507
1 lock held by rcu_tasks_trace/13:
 #0: ffffffff8cd21170 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x30/0xd00 kernel/rcu/tasks.h:507
1 lock held by khungtaskd/28:
 #0: ffffffff8cd207a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3291:
 #0: ffff88814ae94098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
 #1: ffffc90002d232f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6e8/0x1e50 drivers/tty/n_tty.c:2177
3 locks held by kworker/u5:4/3658:
 #0: ffff88807c0ad138 ((wq_completion)hci5){+.+.}-{0:0}, at: process_one_work+0x796/0xd10 kernel/workqueue.c:2262
 #1: ffffc900043dfd00 ((work_completion)(&hdev->cmd_sync_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0xd10 kernel/workqueue.c:2264
 #2: ffff88802a0ccfd0 (&hdev->req_lock){+.+.}-{3:3}, at: hci_cmd_sync_work+0x1f8/0x390 net/bluetooth/hci_sync.c:302
2 locks held by kworker/0:8/15451:
 #0: ffff888012066538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x796/0xd10 kernel/workqueue.c:2262
 #1: ffffc900043bfd00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0xd10 kernel/workqueue.c:2264
2 locks held by syz-executor.0/29005:
 #0: ffff8880744b9a10 (&sb->s_type->i_mutex_key#9){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
 #0: ffff8880744b9a10 (&sb->s_type->i_mutex_key#9){+.+.}-{3:3}, at: __sock_release net/socket.c:649 [inline]
 #0: ffff8880744b9a10 (&sb->s_type->i_mutex_key#9){+.+.}-{3:3}, at: sock_close+0x93/0x260 net/socket.c:1365
 #1: ffffffff8cd25d78 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:292 [inline]
 #1: ffffffff8cd25d78 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x2a4/0x770 kernel/rcu/tree_exp.h:940
2 locks held by syz-executor.4/29007:
 #0: ffff8880746eac10 (&sb->s_type->i_mutex_key#9){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
 #0: ffff8880746eac10 (&sb->s_type->i_mutex_key#9){+.+.}-{3:3}, at: __sock_release net/socket.c:649 [inline]
 #0: ffff8880746eac10 (&sb->s_type->i_mutex_key#9){+.+.}-{3:3}, at: sock_close+0x93/0x260 net/socket.c:1365
 #1: ffffffff8cd25d78 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:324 [inline]
 #1: ffffffff8cd25d78 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x369/0x770 kernel/rcu/tree_exp.h:940
2 locks held by syz-executor.1/29026:
 #0: ffff8880b9a39c18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x25/0x110 kernel/sched/core.c:544
 #1: ffff8880b9b27748 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x5b1/0x8a0 kernel/sched/psi.c:889

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.0.0-rc1-syzkaller-00025-g274a2eebf80c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 nmi_cpu_backtrace+0x47c/0x4b0 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x169/0x280 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
 watchdog+0xcd5/0xd20 kernel/hung_task.c:369
 kthread+0x266/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 13933 Comm: kworker/u4:15 Not tainted 6.0.0-rc1-syzkaller-00025-g274a2eebf80c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:hlock_class kernel/locking/lockdep.c:227 [inline]
RIP: 0010:mark_lock+0xa2/0x350 kernel/locking/lockdep.c:4610
Code: 00 8b 1b 81 e3 ff 1f 00 00 48 89 d8 48 c1 e8 06 48 8d 3c c5 40 d0 f9 8f be 08 00 00 00 e8 86 83 73 00 48 0f a3 1d 0e 1b 90 0e <72> 24 48 c7 c0 40 4f 79 91 48 c1 e8 03 42 8a 04 28 84 c0 0f 85 25
RSP: 0018:ffffc9000303f698 EFLAGS: 00000057
RAX: 0000000000000001 RBX: 0000000000000006 RCX: ffffffff8169b52a
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8ff9d040
RBP: 0000000000000002 R08: dffffc0000000000 R09: fffffbfff1ff3a09
R10: fffffbfff1ff3a09 R11: 1ffffffff1ff3a08 R12: ffff88807bb5e390
R13: dffffc0000000000 R14: 0000000000000004 R15: ffff88807bb5e370
FS:  0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f89b48d5738 CR3: 000000000ca8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 mark_held_locks kernel/locking/lockdep.c:4234 [inline]
 __trace_hardirqs_on_caller kernel/locking/lockdep.c:4252 [inline]
 lockdep_hardirqs_on_prepare+0x280/0x7b0 kernel/locking/lockdep.c:4319
 trace_hardirqs_on+0x34/0x40 kernel/trace/trace_preemptirq.c:49
 __text_poke+0x7c4/0x9d0 arch/x86/kernel/alternative.c:1183
 text_poke arch/x86/kernel/alternative.c:1208 [inline]
 text_poke_bp_batch+0x6bc/0x970 arch/x86/kernel/alternative.c:1554
 text_poke_flush arch/x86/kernel/alternative.c:1660 [inline]
 text_poke_finish+0x16/0x30 arch/x86/kernel/alternative.c:1667
 arch_jump_label_transform_apply+0x13/0x20 arch/x86/kernel/jump_label.c:146
 static_key_enable_cpuslocked+0x129/0x250 kernel/jump_label.c:177
 static_key_enable+0x16/0x20 kernel/jump_label.c:190
 toggle_allocation_gate+0xbf/0x470 mm/kfence/core.c:811
 process_one_work+0x81c/0xd10 kernel/workqueue.c:2289
 worker_thread+0xb14/0x1330 kernel/workqueue.c:2436
 kthread+0x266/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30
 </TASK>

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/08/18 14:07 upstream 274a2eebf80c d58e263f .config console log report info ci-upstream-kasan-gce-smack-root INFO: task hung in hci_cmd_sync_clear
2022/05/31 06:38 upstream 2c5ca23f7414 af70c3a9 .config console log report info ci-upstream-kasan-gce-smack-root INFO: task hung in hci_cmd_sync_clear
2022/04/18 20:27 upstream b2d229d4ddb1 8bcc32a6 .config console log report info ci-upstream-kasan-gce-root INFO: task hung in hci_cmd_sync_clear
2022/03/24 18:42 linux-next dd315b580061 89bc8608 .config console log report info ci-upstream-linux-next-kasan-gce-root INFO: task hung in hci_cmd_sync_clear
* Struck through repros no longer work on HEAD.