======================================================
WARNING: possible circular locking dependency detected
5.10.205 #1 Not tainted
------------------------------------------------------
syz-executor.0/4507 is trying to acquire lock:
ffff88800d9d4ae8 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: __flush_work+0xdd/0xa90 kernel/workqueue.c:3050
netlink: 4 bytes leftover after parsing attributes in process `syz-executor.7'.

but task is already holding lock:
ffff88800d9d4f40 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close+0xef/0x1240 net/bluetooth/hci_core.c:1734

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&hdev->req_lock){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:968 [inline]
       __mutex_lock+0x13d/0x10b0 kernel/locking/mutex.c:1109
       hci_dev_do_close+0xef/0x1240 net/bluetooth/hci_core.c:1734
       hci_rfkill_set_block+0x166/0x1a0 net/bluetooth/hci_core.c:2223
       rfkill_set_block+0x1fd/0x540 net/rfkill/core.c:341
       rfkill_fop_write+0x253/0x4b0 net/rfkill/core.c:1240
       vfs_write+0x29a/0xa70 fs/read_write.c:603
       ksys_write+0x1f6/0x260 fs/read_write.c:658
       do_syscall_64+0x33/0x40 arch/x86/entry/common.c:46
       entry_SYSCALL_64_after_hwframe+0x62/0xc7

-> #2 (rfkill_global_mutex){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:968 [inline]
       __mutex_lock+0x13d/0x10b0 kernel/locking/mutex.c:1109
       rfkill_register+0x36/0xa10 net/rfkill/core.c:1016
       hci_register_dev+0x42e/0xc00 net/bluetooth/hci_core.c:3773
       __vhci_create_device+0x2c8/0x5c0 drivers/bluetooth/hci_vhci.c:129
       vhci_create_device drivers/bluetooth/hci_vhci.c:153 [inline]
       vhci_open_timeout+0x38/0x50 drivers/bluetooth/hci_vhci.c:310
       process_one_work+0x9a9/0x14b0 kernel/workqueue.c:2282
       worker_thread+0x61d/0x1310 kernel/workqueue.c:2428
       kthread+0x38f/0x470 kernel/kthread.c:313
       ret_from_fork+0x22/0x30 arch/x86/entry/entry_64.S:299

-> #1 (&data->open_mutex){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:968 [inline]
       __mutex_lock+0x13d/0x10b0 kernel/locking/mutex.c:1109
       vhci_send_frame+0x63/0xa0 drivers/bluetooth/hci_vhci.c:71
       hci_send_frame+0x1b9/0x320 net/bluetooth/hci_core.c:4060
       hci_sched_acl_pkt net/bluetooth/hci_core.c:4585 [inline]
       hci_sched_acl net/bluetooth/hci_core.c:4670 [inline]
       hci_tx_work+0x10af/0x1660 net/bluetooth/hci_core.c:4741
       process_one_work+0x9a9/0x14b0 kernel/workqueue.c:2282
       worker_thread+0x61d/0x1310 kernel/workqueue.c:2428
       kthread+0x38f/0x470 kernel/kthread.c:313
       ret_from_fork+0x22/0x30 arch/x86/entry/entry_64.S:299

-> #0 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:2988 [inline]
       check_prevs_add kernel/locking/lockdep.c:3113 [inline]
       validate_chain kernel/locking/lockdep.c:3729 [inline]
       __lock_acquire+0x29e7/0x5b00 kernel/locking/lockdep.c:4955
       lock_acquire kernel/locking/lockdep.c:5566 [inline]
       lock_acquire+0x197/0x470 kernel/locking/lockdep.c:5531
       __flush_work+0x105/0xa90 kernel/workqueue.c:3053
       hci_dev_do_close+0x131/0x1240 net/bluetooth/hci_core.c:1745
       hci_rfkill_set_block+0x166/0x1a0 net/bluetooth/hci_core.c:2223
       rfkill_set_block+0x1fd/0x540 net/rfkill/core.c:341
       rfkill_fop_write+0x253/0x4b0 net/rfkill/core.c:1240
       vfs_write+0x29a/0xa70 fs/read_write.c:603
       ksys_write+0x1f6/0x260 fs/read_write.c:658
       do_syscall_64+0x33/0x40 arch/x86/entry/common.c:46
       entry_SYSCALL_64_after_hwframe+0x62/0xc7

other info that might help us debug this:

Chain exists of:
  (work_completion)(&hdev->tx_work) --> rfkill_global_mutex --> &hdev->req_lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&hdev->req_lock);
                               lock(rfkill_global_mutex);
                               lock(&hdev->req_lock);
  lock((work_completion)(&hdev->tx_work));

 *** DEADLOCK ***

2 locks held by syz-executor.0/4507:
 #0: ffffffff85619628 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0xff/0x4b0 net/rfkill/core.c:1232
 #1: ffff88800d9d4f40 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close+0xef/0x1240 net/bluetooth/hci_core.c:1734

stack backtrace:
CPU: 0 PID: 4507 Comm: syz-executor.0 Not tainted 5.10.205 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x107/0x167 lib/dump_stack.c:118
 check_noncircular+0x263/0x2e0 kernel/locking/lockdep.c:2123
 check_prev_add kernel/locking/lockdep.c:2988 [inline]
 check_prevs_add kernel/locking/lockdep.c:3113 [inline]
 validate_chain kernel/locking/lockdep.c:3729 [inline]
 __lock_acquire+0x29e7/0x5b00 kernel/locking/lockdep.c:4955
 lock_acquire kernel/locking/lockdep.c:5566 [inline]
 lock_acquire+0x197/0x470 kernel/locking/lockdep.c:5531
 __flush_work+0x105/0xa90 kernel/workqueue.c:3053
 hci_dev_do_close+0x131/0x1240 net/bluetooth/hci_core.c:1745
 hci_rfkill_set_block+0x166/0x1a0 net/bluetooth/hci_core.c:2223
 rfkill_set_block+0x1fd/0x540 net/rfkill/core.c:341
 rfkill_fop_write+0x253/0x4b0 net/rfkill/core.c:1240
 vfs_write+0x29a/0xa70 fs/read_write.c:603
 ksys_write+0x1f6/0x260 fs/read_write.c:658
 do_syscall_64+0x33/0x40 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x62/0xc7
RIP: 0033:0x7fdf5b036b19
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 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fdf585ac188 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fdf5b149f60 RCX: 00007fdf5b036b19
RDX: 0000000000000008 RSI: 00000000200000c0 RDI: 0000000000000004
RBP: 00007fdf5b090f6d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc0186912f R14: 00007fdf585ac300 R15: 0000000000022000
sd 0:0:0:0: [sg0] tag#0 FAILED Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK cmd_age=0s
sd 0:0:0:0: [sg0] tag#0 CDB: opcode=0x97
sd 0:0:0:0: [sg0] tag#0 CDB[00]: 97 c4 f8 fb 2a f3 2a e4 31 38 4c 83 73 ed ea 06
sd 0:0:0:0: [sg0] tag#0 CDB[10]: 52 b5 93 2c d1 d3 e6 79 18 f8 5d fa 9c 78 0c d4
sd 0:0:0:0: [sg0] tag#0 CDB[20]: 92 0a 14 af cd 09 15 06 e4 91 49 b0 5a 97 05 01
sd 0:0:0:0: [sg0] tag#0 CDB[30]: 9b d7 aa d6 9b ce 85 6a 13 3b 32 e9 89 93 e7 ec
sd 0:0:0:0: [sg0] tag#0 CDB[40]: 33 5e 15 1a aa ba 2f 1e e7 ca 8f a4 14 92 bc b6
sd 0:0:0:0: [sg0] tag#0 CDB[50]: aa 39 8d 49 55 5a 36 eb 4b ab d3 b0 23 fd 3b 33
sd 0:0:0:0: [sg0] tag#0 CDB[60]: a2 e9 fc db 95 c2 05 5a 5e b7 05 0e fe 1d e6 82
sd 0:0:0:0: [sg0] tag#0 CDB[70]: 9d a4 ac fd 04 c7 b1 92 7e 7c 55 62 df 8f c0 e3
sd 0:0:0:0: [sg0] tag#0 CDB[80]: 75 22
sd 0:0:0:0: [sg0] tag#0 FAILED Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK cmd_age=0s
sd 0:0:0:0: [sg0] tag#0 CDB: opcode=0x97
sd 0:0:0:0: [sg0] tag#0 CDB[00]: 97 c4 f8 fb 2a f3 2a e4 31 38 4c 83 73 ed ea 06
sd 0:0:0:0: [sg0] tag#0 CDB[10]: 52 b5 93 2c d1 d3 e6 79 18 f8 5d fa 9c 78 0c d4
sd 0:0:0:0: [sg0] tag#0 CDB[20]: 92 0a 14 af cd 09 15 06 e4 91 49 b0 5a 97 05 01
sd 0:0:0:0: [sg0] tag#0 CDB[30]: 9b d7 aa d6 9b ce 85 6a 13 3b 32 e9 89 93 e7 ec
sd 0:0:0:0: [sg0] tag#0 CDB[40]: 33 5e 15 1a aa ba 2f 1e e7 ca 8f a4 14 92 bc b6
sd 0:0:0:0: [sg0] tag#0 CDB[50]: aa 39 8d 49 55 5a 36 eb 4b ab d3 b0 23 fd 3b 33
sd 0:0:0:0: [sg0] tag#0 CDB[60]: a2 e9 fc db 95 c2 05 5a 5e b7 05 0e fe 1d e6 82
sd 0:0:0:0: [sg0] tag#0 CDB[70]: 9d a4 ac fd 04 c7 b1 92 7e 7c 55 62 df 8f c0 e3
sd 0:0:0:0: [sg0] tag#0 CDB[80]: 75 22
netlink: 16 bytes leftover after parsing attributes in process `syz-executor.3'.
EXT4-fs (loop6): Unrecognized mount option "" or missing value
FAT-fs (loop5): Unrecognized mount option "/dev/vcsu" or missing value
FAT-fs (loop5): Unrecognized mount option "/dev/vcsu" or missing value