======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
krfcommd/3266 is trying to acquire lock:
ffff88810018d948 ((wq_completion)hci2#2){+.+.}-{0:0}, at: touch_wq_lockdep_map+0xb5/0x180

but task is already holding lock:
ffffffff913fdde0 (rfcomm_mutex){+.+.}-{4:4}, at: rfcomm_process_sessions+0x2c6/0x9690

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (rfcomm_mutex){+.+.}-{4:4}:
       __mutex_lock+0x197/0x15a0
       rfcomm_security_cfm+0x90/0x820
       hci_encrypt_cfm+0x30d/0x420
       hci_encrypt_change_evt+0x67f/0xde0
       hci_event_packet+0x6cd/0xf10
       hci_rx_work+0x2b4/0x1110
       process_scheduled_works+0xc3d/0x1630
       worker_thread+0xa47/0xfb0
       kthread+0x38b/0x480
       ret_from_fork+0x514/0xb70
       ret_from_fork_asm+0x1a/0x30

-> #3 (hci_cb_list_lock){+.+.}-{4:4}:
       __mutex_lock+0x197/0x15a0
       hci_remote_features_evt+0x53d/0x950
       hci_event_packet+0x6cd/0xf10
       hci_rx_work+0x2b4/0x1110
       process_scheduled_works+0xc3d/0x1630
       worker_thread+0xa47/0xfb0
       kthread+0x38b/0x480
       ret_from_fork+0x514/0xb70
       ret_from_fork_asm+0x1a/0x30

-> #2 (&hdev->lock){+.+.}-{4:4}:
       __mutex_lock+0x197/0x15a0
       hci_cmd_work+0xa0/0x850
       process_scheduled_works+0xc3d/0x1630
       worker_thread+0xa47/0xfb0
       kthread+0x38b/0x480
       ret_from_fork+0x514/0xb70
       ret_from_fork_asm+0x1a/0x30

-> #1 ((work_completion)(&hdev->cmd_work)){+.+.}-{0:0}:
       process_scheduled_works+0xc03/0x1630
       worker_thread+0xa47/0xfb0
       kthread+0x38b/0x480
       ret_from_fork+0x514/0xb70
       ret_from_fork_asm+0x1a/0x30

-> #0 ((wq_completion)hci2#2){+.+.}-{0:0}:
       __lock_acquire+0x164c/0x2de0
       lock_acquire+0x115/0x350
       touch_wq_lockdep_map+0xcb/0x180
       __flush_workqueue+0x148/0x10b0
       drain_workqueue+0xce/0x380
       destroy_workqueue+0xbe/0x7b0
       hci_release_dev+0xe3/0x1510
       bt_host_release+0x93/0xa0
       device_release+0xc4/0x1f0
       kobject_put+0x222/0x550
       device_release+0xc4/0x1f0
       kobject_put+0x222/0x550
       l2cap_chan_put+0x1fd/0x350
       l2cap_sock_release+0x1a2/0x230
       sock_release+0x85/0x150
       rfcomm_session_del+0x14b/0x270
       rfcomm_process_sessions+0x7456/0x9690
       rfcomm_run+0x3f5/0x620
       kthread+0x38b/0x480
       ret_from_fork+0x514/0xb70
       ret_from_fork_asm+0x1a/0x30

other info that might help us debug this:

Chain exists of:
  (wq_completion)hci2#2 --> hci_cb_list_lock --> rfcomm_mutex

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(rfcomm_mutex);
                               lock(hci_cb_list_lock);
                               lock(rfcomm_mutex);
  lock((wq_completion)hci2#2);

 *** DEADLOCK ***

locks held by krfcommd/3266: 1, last CPU#1:
 #0: ffffffff913fdde0 (rfcomm_mutex){+.+.}-{4:4}, at: rfcomm_process_sessions+0x2c6/0x9690

stack backtrace:
CPU: 1 UID: 0 PID: 3266 Comm: krfcommd Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150
 print_circular_bug+0x2e2/0x300
 check_noncircular+0x12f/0x150
 __lock_acquire+0x164c/0x2de0
 lock_acquire+0x115/0x350
 touch_wq_lockdep_map+0xcb/0x180
 __flush_workqueue+0x148/0x10b0
 drain_workqueue+0xce/0x380
 destroy_workqueue+0xbe/0x7b0
 hci_release_dev+0xe3/0x1510
 bt_host_release+0x93/0xa0
 device_release+0xc4/0x1f0
 kobject_put+0x222/0x550
 device_release+0xc4/0x1f0
 kobject_put+0x222/0x550
 l2cap_chan_put+0x1fd/0x350
 l2cap_sock_release+0x1a2/0x230
 sock_release+0x85/0x150
 rfcomm_session_del+0x14b/0x270
 rfcomm_process_sessions+0x7456/0x9690
 rfcomm_run+0x3f5/0x620
 kthread+0x38b/0x480
 ret_from_fork+0x514/0xb70
 ret_from_fork_asm+0x1a/0x30
 </TASK>
