Buffer I/O error on dev sr0, logical block 6, async page read sr 1:0:0:0: [sr0] tag#0 unaligned transfer Buffer I/O error on dev sr0, logical block 7, async page read ====================================================== WARNING: possible circular locking dependency detected 5.19.0-rc1-next-20220610 #1 Not tainted ------------------------------------------------------ syz-executor.3/60600 is trying to acquire lock: ffff888017ecf130 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_conn_del+0x11c/0x2c0 but task is already holding lock: ffffffff857d9568 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xc7/0x230 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+0x136/0x14c0 hci_remote_features_evt+0x59d/0x990 hci_event_packet+0x779/0xee0 hci_rx_work+0x24c/0xb90 process_one_work+0xa1c/0x16a0 worker_thread+0x637/0x1250 kthread+0x2f2/0x3b0 ret_from_fork+0x22/0x30 -> #1 (&hdev->lock){+.+.}-{3:3}: __mutex_lock+0x136/0x14c0 sco_sock_connect+0x1e0/0xa60 __sys_connect_file+0x151/0x190 __sys_connect+0x161/0x190 __x64_sys_connect+0x6f/0xb0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 -> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}: __lock_acquire+0x2c2f/0x6120 lock_acquire+0x1a2/0x530 lock_sock_nested+0x3d/0xf0 sco_conn_del+0x11c/0x2c0 sco_disconn_cfm+0x62/0x80 hci_conn_hash_flush+0x119/0x230 hci_dev_close_sync+0x4e8/0xf20 hci_unregister_dev+0x14f/0x3e0 vhci_release+0x7c/0xf0 __fput+0x272/0x9d0 task_work_run+0xe2/0x1a0 do_exit+0xafd/0x27f0 do_group_exit+0xd2/0x2f0 get_signal+0x2201/0x24b0 arch_do_signal_or_restart+0x89/0x1bf0 exit_to_user_mode_prepare+0x131/0x1a0 syscall_exit_to_user_mode+0x19/0x40 do_syscall_64+0x48/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 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 *** 3 locks held by syz-executor.3/60600: #0: ffff888019bb1048 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x147/0x3e0 #1: ffff888019bb0078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x24d/0xf20 #2: ffffffff857d9568 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xc7/0x230 stack backtrace: CPU: 1 PID: 60600 Comm: syz-executor.3 Not tainted 5.19.0-rc1-next-20220610 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 Call Trace: dump_stack_lvl+0x8b/0xb3 check_noncircular+0x25f/0x2e0 __lock_acquire+0x2c2f/0x6120 lock_acquire+0x1a2/0x530 lock_sock_nested+0x3d/0xf0 sco_conn_del+0x11c/0x2c0 sco_disconn_cfm+0x62/0x80 hci_conn_hash_flush+0x119/0x230 hci_dev_close_sync+0x4e8/0xf20 hci_unregister_dev+0x14f/0x3e0 vhci_release+0x7c/0xf0 __fput+0x272/0x9d0 task_work_run+0xe2/0x1a0 do_exit+0xafd/0x27f0 do_group_exit+0xd2/0x2f0 get_signal+0x2201/0x24b0 arch_do_signal_or_restart+0x89/0x1bf0 exit_to_user_mode_prepare+0x131/0x1a0 syscall_exit_to_user_mode+0x19/0x40 do_syscall_64+0x48/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP: 0033:0x7fc0b406db19 Code: Unable to access opcode bytes at RIP 0x7fc0b406daef. RSP: 002b:00007fc0b15e3188 EFLAGS: 00000246 ORIG_RAX: 0000000000000009 RAX: 0000000020ffc000 RBX: 00007fc0b4180f60 RCX: 00007fc0b406db19 RDX: 0000000001000004 RSI: 0000000000002000 RDI: 0000000020ffc000 RBP: 00007fc0b40c7f6d R08: 0000000000000005 R09: 0000000000000000 R10: 0000000000002811 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffcac591eff R14: 00007fc0b15e3300 R15: 0000000000022000