Bluetooth: hci3: hardware error 0x00 ====================================================== WARNING: possible circular locking dependency detected 6.1.60-syzkaller #0 Not tainted ------------------------------------------------------ kworker/u5:6/3573 is trying to acquire lock: ffff888022708130 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1744 [inline] ffff888022708130 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_conn_del+0x104/0x300 net/bluetooth/sco.c:197 but task is already holding lock: ffffffff8e3ebea8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1796 [inline] ffffffff8e3ebea8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xb8/0x2a0 net/bluetooth/hci_conn.c:2504 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (hci_cb_list_lock){+.+.}-{3:3}: lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x132/0xd80 kernel/locking/mutex.c:747 hci_connect_cfm include/net/bluetooth/hci_core.h:1781 [inline] hci_remote_features_evt+0x66c/0xac0 net/bluetooth/hci_event.c:3769 hci_event_func net/bluetooth/hci_event.c:7496 [inline] hci_event_packet+0xaa1/0x1510 net/bluetooth/hci_event.c:7548 hci_rx_work+0x3cd/0xce0 net/bluetooth/hci_core.c:4093 process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292 worker_thread+0xa47/0x1200 kernel/workqueue.c:2439 kthread+0x28d/0x320 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 -> #1 (&hdev->lock){+.+.}-{3:3}: lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x132/0xd80 kernel/locking/mutex.c:747 sco_sock_connect+0x181/0x8f0 net/bluetooth/sco.c:593 __sys_connect_file net/socket.c:1993 [inline] __sys_connect+0x2c9/0x300 net/socket.c:2010 __do_sys_connect net/socket.c:2020 [inline] __se_sys_connect net/socket.c:2017 [inline] __x64_sys_connect+0x76/0x80 net/socket.c:2017 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3824 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5048 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 lock_sock_nested+0x44/0x100 net/core/sock.c:3475 lock_sock include/net/sock.h:1744 [inline] sco_conn_del+0x104/0x300 net/bluetooth/sco.c:197 hci_disconn_cfm include/net/bluetooth/hci_core.h:1799 [inline] hci_conn_hash_flush+0x10e/0x2a0 net/bluetooth/hci_conn.c:2504 hci_dev_close_sync+0x9a9/0xfc0 net/bluetooth/hci_sync.c:4975 hci_dev_do_close net/bluetooth/hci_core.c:554 [inline] hci_error_reset+0x104/0x250 net/bluetooth/hci_core.c:1059 process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292 worker_thread+0xa47/0x1200 kernel/workqueue.c:2439 kthread+0x28d/0x320 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 other info that might help us debug this: Chain exists of: sk_lock-AF_BLUETOOTH-BTPROTO_SCO --> &hdev->lock --> hci_cb_list_lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(hci_cb_list_lock); lock(&hdev->lock); lock(hci_cb_list_lock); lock(sk_lock-AF_BLUETOOTH-BTPROTO_SCO); *** DEADLOCK *** 5 locks held by kworker/u5:6/3573: #0: ffff88807baac938 ((wq_completion)hci3){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267 #1: ffffc90003d1fd20 ((work_completion)(&hdev->error_reset)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267 #2: ffff88807d7f90b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:552 [inline] #2: ffff88807d7f90b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_error_reset+0xfc/0x250 net/bluetooth/hci_core.c:1059 #3: ffff88807d7f8078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x48d/0xfc0 net/bluetooth/hci_sync.c:4962 #4: ffffffff8e3ebea8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1796 [inline] #4: ffffffff8e3ebea8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xb8/0x2a0 net/bluetooth/hci_conn.c:2504 stack backtrace: CPU: 1 PID: 3573 Comm: kworker/u5:6 Not tainted 6.1.60-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023 Workqueue: hci3 hci_error_reset Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 check_noncircular+0x2fa/0x3b0 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3824 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5048 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 lock_sock_nested+0x44/0x100 net/core/sock.c:3475 lock_sock include/net/sock.h:1744 [inline] sco_conn_del+0x104/0x300 net/bluetooth/sco.c:197 hci_disconn_cfm include/net/bluetooth/hci_core.h:1799 [inline] hci_conn_hash_flush+0x10e/0x2a0 net/bluetooth/hci_conn.c:2504 hci_dev_close_sync+0x9a9/0xfc0 net/bluetooth/hci_sync.c:4975 hci_dev_do_close net/bluetooth/hci_core.c:554 [inline] hci_error_reset+0x104/0x250 net/bluetooth/hci_core.c:1059 process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292 worker_thread+0xa47/0x1200 kernel/workqueue.c:2439 kthread+0x28d/0x320 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 Bluetooth: hci3: Opcode 0x c03 failed: -110 Bluetooth: hci3: hardware error 0x00 Bluetooth: hci3: Opcode 0x c03 failed: -110 Bluetooth: hci3: hardware error 0x00 Bluetooth: hci3: Opcode 0x c03 failed: -110 Bluetooth: hci3: hardware error 0x00 Bluetooth: hci3: Opcode 0x c03 failed: -110 Bluetooth: hci3: hardware error 0x00