====================================================== WARNING: possible circular locking dependency detected 6.1.32-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor970/4253 is trying to acquire lock: ffff0000dcd74130 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1721 [inline] ffff0000dcd74130 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_conn_del+0xec/0x498 net/bluetooth/sco.c:197 but task is already holding lock: ffff800017cdb948 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1790 [inline] ffff800017cdb948 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xb0/0x264 net/bluetooth/hci_conn.c:2455 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (hci_cb_list_lock){+.+.}-{3:3}: __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 hci_connect_cfm include/net/bluetooth/hci_core.h:1775 [inline] hci_remote_features_evt+0x458/0x8a8 net/bluetooth/hci_event.c:3753 hci_event_func net/bluetooth/hci_event.c:7476 [inline] hci_event_packet+0x644/0xf3c net/bluetooth/hci_event.c:7528 hci_rx_work+0x32c/0x8b8 net/bluetooth/hci_core.c:4058 process_one_work+0x7ac/0x1404 kernel/workqueue.c:2289 worker_thread+0x8e4/0xfec kernel/workqueue.c:2436 kthread+0x250/0x2d8 kernel/kthread.c:376 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860 -> #1 (&hdev->lock){+.+.}-{3:3}: __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 sco_sock_connect+0x170/0x838 net/bluetooth/sco.c:593 __sys_connect_file net/socket.c:1976 [inline] __sys_connect+0x268/0x290 net/socket.c:1993 __do_sys_connect net/socket.c:2003 [inline] __se_sys_connect net/socket.c:2000 [inline] __arm64_sys_connect+0x7c/0x94 net/socket.c:2000 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581 -> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain kernel/locking/lockdep.c:3832 [inline] __lock_acquire+0x3338/0x764c kernel/locking/lockdep.c:5056 lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5669 lock_sock_nested+0x78/0x138 net/core/sock.c:3458 lock_sock include/net/sock.h:1721 [inline] sco_conn_del+0xec/0x498 net/bluetooth/sco.c:197 sco_disconn_cfm+0x8c/0xdc net/bluetooth/sco.c:1381 hci_disconn_cfm include/net/bluetooth/hci_core.h:1793 [inline] hci_conn_hash_flush+0x104/0x264 net/bluetooth/hci_conn.c:2455 hci_dev_close_sync+0x894/0xf8c net/bluetooth/hci_sync.c:4880 hci_dev_do_close net/bluetooth/hci_core.c:554 [inline] hci_rfkill_set_block+0xec/0x1e0 net/bluetooth/hci_core.c:956 rfkill_set_block+0x18c/0x37c net/rfkill/core.c:345 rfkill_fop_write+0x578/0x734 net/rfkill/core.c:1286 vfs_write+0x2a4/0x914 fs/read_write.c:582 ksys_write+0x15c/0x26c fs/read_write.c:637 __do_sys_write fs/read_write.c:649 [inline] __se_sys_write fs/read_write.c:646 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:646 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581 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 syz-executor970/4253: #0: ffff800017e2ec88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0x234/0x734 net/rfkill/core.c:1278 #1: ffff0000d45f5028 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:552 [inline] #1: ffff0000d45f5028 (&hdev->req_lock){+.+.}-{3:3}, at: hci_rfkill_set_block+0xe4/0x1e0 net/bluetooth/hci_core.c:956 #2: ffff0000d45f4078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x39c/0xf8c net/bluetooth/hci_sync.c:4867 #3: ffff800017cdb948 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1790 [inline] #3: ffff800017cdb948 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xb0/0x264 net/bluetooth/hci_conn.c:2455 stack backtrace: CPU: 0 PID: 4253 Comm: syz-executor970 Not tainted 6.1.32-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023 Call trace: dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106 dump_stack+0x1c/0x58 lib/dump_stack.c:113 print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2056 check_noncircular+0x2cc/0x378 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain kernel/locking/lockdep.c:3832 [inline] __lock_acquire+0x3338/0x764c kernel/locking/lockdep.c:5056 lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5669 lock_sock_nested+0x78/0x138 net/core/sock.c:3458 lock_sock include/net/sock.h:1721 [inline] sco_conn_del+0xec/0x498 net/bluetooth/sco.c:197 sco_disconn_cfm+0x8c/0xdc net/bluetooth/sco.c:1381 hci_disconn_cfm include/net/bluetooth/hci_core.h:1793 [inline] hci_conn_hash_flush+0x104/0x264 net/bluetooth/hci_conn.c:2455 hci_dev_close_sync+0x894/0xf8c net/bluetooth/hci_sync.c:4880 hci_dev_do_close net/bluetooth/hci_core.c:554 [inline] hci_rfkill_set_block+0xec/0x1e0 net/bluetooth/hci_core.c:956 rfkill_set_block+0x18c/0x37c net/rfkill/core.c:345 rfkill_fop_write+0x578/0x734 net/rfkill/core.c:1286 vfs_write+0x2a4/0x914 fs/read_write.c:582 ksys_write+0x15c/0x26c fs/read_write.c:637 __do_sys_write fs/read_write.c:649 [inline] __se_sys_write fs/read_write.c:646 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:646 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581