====================================================== WARNING: possible circular locking dependency detected 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Not tainted ------------------------------------------------------ kworker/1:3/5291 is trying to acquire lock: ffff888026ceb258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1609 [inline] ffff888026ceb258 (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: ffff88802deb9928 (&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: -> #3 (&d->lock){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 __rfcomm_dlc_close+0x235/0x700 net/bluetooth/rfcomm/core.c:491 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+0xb3/0x270 net/socket.c:658 sock_close+0x1c/0x30 net/socket.c:1426 __fput+0x3f9/0xb60 fs/file_table.c:431 delayed_fput+0x72/0x90 fs/file_table.c:454 process_one_work+0x9c8/0x1ba0 kernel/workqueue.c:3229 process_scheduled_works kernel/workqueue.c:3310 [inline] worker_thread+0x6c8/0xf00 kernel/workqueue.c:3391 kthread+0x2c4/0x3a0 kernel/kthread.c:389 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 -> #2 (rfcomm_mutex){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 rfcomm_dlc_exists+0x5f/0x1a0 net/bluetooth/rfcomm/core.c:546 __rfcomm_create_dev net/bluetooth/rfcomm/tty.c:414 [inline] rfcomm_create_dev net/bluetooth/rfcomm/tty.c:485 [inline] rfcomm_dev_ioctl+0x9e6/0x1ca0 net/bluetooth/rfcomm/tty.c:584 rfcomm_sock_ioctl+0xb4/0xe0 net/bluetooth/rfcomm/sock.c:869 sock_do_ioctl+0x119/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+0x192/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_ioctl_mutex){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 rfcomm_create_dev net/bluetooth/rfcomm/tty.c:484 [inline] rfcomm_dev_ioctl+0x905/0x1ca0 net/bluetooth/rfcomm/tty.c:584 rfcomm_sock_ioctl+0xb4/0xe0 net/bluetooth/rfcomm/sock.c:869 sock_do_ioctl+0x119/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+0x192/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+0x28f/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+0xb3/0x270 net/socket.c:658 sock_close+0x1c/0x30 net/socket.c:1426 __fput+0x3f9/0xb60 fs/file_table.c:431 delayed_fput+0x72/0x90 fs/file_table.c:454 process_one_work+0x9c8/0x1ba0 kernel/workqueue.c:3229 process_scheduled_works kernel/workqueue.c:3310 [inline] worker_thread+0x6c8/0xf00 kernel/workqueue.c:3391 kthread+0x2c4/0x3a0 kernel/kthread.c:389 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 other info that might help us debug this: Chain exists of: sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM --> rfcomm_mutex --> &d->lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&d->lock); lock(rfcomm_mutex); lock(&d->lock); lock(sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM); *** DEADLOCK *** 5 locks held by kworker/1:3/5291: #0: ffff88801b078948 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x129b/0x1ba0 kernel/workqueue.c:3204 #1: ffffc9000496fd80 ((delayed_fput_work).work){+.+.}-{0:0}, at: process_one_work+0x921/0x1ba0 kernel/workqueue.c:3205 #2: ffff88805aebbe08 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:815 [inline] #2: ffff88805aebbe08 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: __sock_release+0x86/0x270 net/socket.c:657 #3: ffffffff901756c8 (rfcomm_mutex){+.+.}-{3:3}, at: rfcomm_dlc_close+0x33/0x240 net/bluetooth/rfcomm/core.c:511 #4: ffff88802deb9928 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x235/0x700 net/bluetooth/rfcomm/core.c:491 stack backtrace: CPU: 1 UID: 0 PID: 5291 Comm: kworker/1:3 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: events delayed_fput 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+0x28f/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+0xb3/0x270 net/socket.c:658 sock_close+0x1c/0x30 net/socket.c:1426 __fput+0x3f9/0xb60 fs/file_table.c:431 delayed_fput+0x72/0x90 fs/file_table.c:454 process_one_work+0x9c8/0x1ba0 kernel/workqueue.c:3229 process_scheduled_works kernel/workqueue.c:3310 [inline] worker_thread+0x6c8/0xf00 kernel/workqueue.c:3391 kthread+0x2c4/0x3a0 kernel/kthread.c:389 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 usb 1-1: USB disconnect, device number 6