====================================================== WARNING: possible circular locking dependency detected 6.12.0-rc2-syzkaller-00061-gb983b271662b #0 Not tainted ------------------------------------------------------ syz.1.1890/19549 is trying to acquire lock: ffff888072215258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1609 [inline] ffff888072215258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sk_state_change+0x6d/0x3b0 net/bluetooth/rfcomm/sock.c:73 but task is already holding lock: ffff88804e50cd28 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x235/0x700 net/bluetooth/rfcomm/core.c:491 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&d->lock){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 __rfcomm_dev_add net/bluetooth/rfcomm/tty.c:277 [inline] rfcomm_dev_add net/bluetooth/rfcomm/tty.c:325 [inline] __rfcomm_create_dev net/bluetooth/rfcomm/tty.c:424 [inline] rfcomm_create_dev net/bluetooth/rfcomm/tty.c:485 [inline] rfcomm_dev_ioctl+0x1115/0x1ca0 net/bluetooth/rfcomm/tty.c:584 rfcomm_sock_ioctl+0xb4/0xe0 net/bluetooth/rfcomm/sock.c:869 sock_do_ioctl+0x116/0x280 net/socket.c:1227 sock_ioctl+0x228/0x6c0 net/socket.c:1346 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl fs/ioctl.c:893 [inline] __x64_sys_ioctl+0x18f/0x220 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (rfcomm_dev_lock){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 rfcomm_dev_get+0x6e/0x2b0 net/bluetooth/rfcomm/tty.c:163 rfcomm_get_dev_info net/bluetooth/rfcomm/tty.c:561 [inline] rfcomm_dev_ioctl+0x378/0x1ca0 net/bluetooth/rfcomm/tty.c:593 rfcomm_sock_ioctl+0xb4/0xe0 net/bluetooth/rfcomm/sock.c:869 sock_do_ioctl+0x116/0x280 net/socket.c:1227 sock_ioctl+0x228/0x6c0 net/socket.c:1346 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl fs/ioctl.c:893 [inline] __x64_sys_ioctl+0x18f/0x220 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x250b/0x3ce0 kernel/locking/lockdep.c:5202 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5825 lock_sock_nested+0x3a/0xf0 net/core/sock.c:3611 lock_sock include/net/sock.h:1609 [inline] rfcomm_sk_state_change+0x6d/0x3b0 net/bluetooth/rfcomm/sock.c:73 __rfcomm_dlc_close+0x28c/0x700 net/bluetooth/rfcomm/core.c:493 rfcomm_dlc_close+0x1eb/0x240 net/bluetooth/rfcomm/core.c:524 __rfcomm_sock_close+0xa7/0x230 net/bluetooth/rfcomm/sock.c:220 rfcomm_sock_shutdown+0xd5/0x230 net/bluetooth/rfcomm/sock.c:901 rfcomm_sock_release+0x5d/0x140 net/bluetooth/rfcomm/sock.c:922 __sock_release+0xb0/0x270 net/socket.c:658 sock_close+0x1c/0x30 net/socket.c:1426 __fput+0x3f6/0xb60 fs/file_table.c:431 task_work_run+0x14e/0x250 kernel/task_work.c:228 get_signal+0x1ca/0x2770 kernel/signal.c:2690 arch_do_signal_or_restart+0x90/0x7e0 arch/x86/kernel/signal.c:337 exit_to_user_mode_loop kernel/entry/common.c:111 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] syscall_exit_to_user_mode+0x150/0x2a0 kernel/entry/common.c:218 do_syscall_64+0xda/0x250 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Chain exists of: sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM --> rfcomm_dev_lock --> &d->lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&d->lock); lock(rfcomm_dev_lock); lock(&d->lock); lock(sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM); *** DEADLOCK *** 3 locks held by syz.1.1890/19549: #0: ffff8880799d7a08 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:815 [inline] #0: ffff8880799d7a08 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: __sock_release+0x86/0x270 net/socket.c:657 #1: ffffffff90173448 (rfcomm_mutex){+.+.}-{3:3}, at: rfcomm_dlc_close+0x33/0x240 net/bluetooth/rfcomm/core.c:511 #2: ffff88804e50cd28 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x235/0x700 net/bluetooth/rfcomm/core.c:491 stack backtrace: CPU: 1 UID: 0 PID: 19549 Comm: syz.1.1890 Not tainted 6.12.0-rc2-syzkaller-00061-gb983b271662b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x41c/0x610 kernel/locking/lockdep.c:2074 check_noncircular+0x31a/0x400 kernel/locking/lockdep.c:2206 check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x250b/0x3ce0 kernel/locking/lockdep.c:5202 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5825 lock_sock_nested+0x3a/0xf0 net/core/sock.c:3611 lock_sock include/net/sock.h:1609 [inline] rfcomm_sk_state_change+0x6d/0x3b0 net/bluetooth/rfcomm/sock.c:73 __rfcomm_dlc_close+0x28c/0x700 net/bluetooth/rfcomm/core.c:493 rfcomm_dlc_close+0x1eb/0x240 net/bluetooth/rfcomm/core.c:524 __rfcomm_sock_close+0xa7/0x230 net/bluetooth/rfcomm/sock.c:220 rfcomm_sock_shutdown+0xd5/0x230 net/bluetooth/rfcomm/sock.c:901 rfcomm_sock_release+0x5d/0x140 net/bluetooth/rfcomm/sock.c:922 __sock_release+0xb0/0x270 net/socket.c:658 sock_close+0x1c/0x30 net/socket.c:1426 __fput+0x3f6/0xb60 fs/file_table.c:431 task_work_run+0x14e/0x250 kernel/task_work.c:228 get_signal+0x1ca/0x2770 kernel/signal.c:2690 arch_do_signal_or_restart+0x90/0x7e0 arch/x86/kernel/signal.c:337 exit_to_user_mode_loop kernel/entry/common.c:111 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] syscall_exit_to_user_mode+0x150/0x2a0 kernel/entry/common.c:218 do_syscall_64+0xda/0x250 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f1fc5b7dff9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f1fc6982038 EFLAGS: 00000246 ORIG_RAX: 000000000000002a RAX: fffffffffffffffc RBX: 00007f1fc5d35f80 RCX: 00007f1fc5b7dff9 RDX: 0000000000000080 RSI: 0000000020000300 RDI: 0000000000000004 RBP: 00007f1fc5bf0296 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f1fc5d35f80 R15: 00007ffc0fa809d8