====================================================== WARNING: possible circular locking dependency detected 6.2.0-rc1-syzkaller #0 Not tainted ------------------------------------------------------ kworker/u5:2/5242 is trying to acquire lock: ffff88806533a130 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1725 [inline] ffff88806533a130 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_conn_del+0xfe/0x2f0 net/bluetooth/sco.c:197 but task is already holding lock: ffffffff8e7be368 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_connect_cfm include/net/bluetooth/hci_core.h:1775 [inline] ffffffff8e7be368 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_sco_setup+0xc5/0x550 net/bluetooth/hci_conn.c:633 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+0x1a7/0x400 kernel/locking/lockdep.c:5668 __mutex_lock_common+0x1de/0x26c0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799 hci_connect_cfm include/net/bluetooth/hci_core.h:1775 [inline] hci_remote_features_evt+0x610/0xa60 net/bluetooth/hci_event.c:3768 hci_event_func net/bluetooth/hci_event.c:7482 [inline] hci_event_packet+0x842/0x10c0 net/bluetooth/hci_event.c:7534 hci_rx_work+0x2fc/0x4a0 net/bluetooth/hci_core.c:4043 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 arch/x86/entry/entry_64.S:308 -> #1 (&hdev->lock){+.+.}-{3:3}: lock_acquire+0x1a7/0x400 kernel/locking/lockdep.c:5668 __mutex_lock_common+0x1de/0x26c0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799 sco_sock_connect+0x168/0x350 net/bluetooth/sco.c:593 __sys_connect_file net/socket.c:1976 [inline] __sys_connect+0x29b/0x2d0 net/socket.c:1993 __do_sys_connect net/socket.c:2003 [inline] __se_sys_connect net/socket.c:2000 [inline] __x64_sys_connect+0x76/0x80 net/socket.c:2000 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 -> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain+0x184a/0x6470 kernel/locking/lockdep.c:3831 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055 lock_acquire+0x1a7/0x400 kernel/locking/lockdep.c:5668 lock_sock_nested+0x44/0xf0 net/core/sock.c:3470 lock_sock include/net/sock.h:1725 [inline] sco_conn_del+0xfe/0x2f0 net/bluetooth/sco.c:197 hci_connect_cfm include/net/bluetooth/hci_core.h:1778 [inline] hci_sco_setup+0x142/0x550 net/bluetooth/hci_conn.c:633 hci_conn_complete_evt+0xa50/0x1360 net/bluetooth/hci_event.c:3244 hci_event_func net/bluetooth/hci_event.c:7482 [inline] hci_event_packet+0x842/0x10c0 net/bluetooth/hci_event.c:7534 hci_rx_work+0x2fc/0x4a0 net/bluetooth/hci_core.c:4043 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 arch/x86/entry/entry_64.S:308 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 *** 4 locks held by kworker/u5:2/5242: #0: ffff8880650a6938 ((wq_completion)hci0#2){+.+.}-{0:0}, at: process_one_work+0x796/0xd10 kernel/workqueue.c:2262 #1: ffffc900049efd00 ((work_completion)(&hdev->rx_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0xd10 kernel/workqueue.c:2264 #2: ffff888077bdc078 (&hdev->lock){+.+.}-{3:3}, at: hci_conn_complete_evt+0xb0/0x1360 net/bluetooth/hci_event.c:3140 #3: ffffffff8e7be368 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_connect_cfm include/net/bluetooth/hci_core.h:1775 [inline] #3: ffffffff8e7be368 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_sco_setup+0xc5/0x550 net/bluetooth/hci_conn.c:633 stack backtrace: CPU: 1 PID: 5242 Comm: kworker/u5:2 Not tainted 6.2.0-rc1-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Workqueue: hci0 hci_rx_work Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106 check_noncircular+0x2f9/0x3b0 kernel/locking/lockdep.c:2177 check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain+0x184a/0x6470 kernel/locking/lockdep.c:3831 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055 lock_acquire+0x1a7/0x400 kernel/locking/lockdep.c:5668 lock_sock_nested+0x44/0xf0 net/core/sock.c:3470 lock_sock include/net/sock.h:1725 [inline] sco_conn_del+0xfe/0x2f0 net/bluetooth/sco.c:197 hci_connect_cfm include/net/bluetooth/hci_core.h:1778 [inline] hci_sco_setup+0x142/0x550 net/bluetooth/hci_conn.c:633 hci_conn_complete_evt+0xa50/0x1360 net/bluetooth/hci_event.c:3244 hci_event_func net/bluetooth/hci_event.c:7482 [inline] hci_event_packet+0x842/0x10c0 net/bluetooth/hci_event.c:7534 hci_rx_work+0x2fc/0x4a0 net/bluetooth/hci_core.c:4043 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 arch/x86/entry/entry_64.S:308 Bluetooth: hci0: command 0x0409 tx timeout Bluetooth: hci1: Opcode 0x c03 failed: -110