BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
turning off the locking correctness validator.
CPU: 0 PID: 8180 Comm: kworker/u5:1 Not tainted 5.5.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: hci2 hci_power_on
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x12d/0x187 lib/dump_stack.c:118
 add_chain_cache kernel/locking/lockdep.c:2840 [inline]
 lookup_chain_cache_add kernel/locking/lockdep.c:2914 [inline]
 validate_chain kernel/locking/lockdep.c:2935 [inline]
 __lock_acquire.cold.65+0x18/0x385 kernel/locking/lockdep.c:3954
 lock_acquire+0x194/0x410 kernel/locking/lockdep.c:4484
 __mutex_lock_common kernel/locking/mutex.c:956 [inline]
 __mutex_lock+0x155/0x1410 kernel/locking/mutex.c:1103
 mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:1118
 drain_workqueue+0x22/0x340 kernel/workqueue.c:2935
 hci_dev_do_close+0x1d8/0xe30 net/bluetooth/hci_core.c:1714
 hci_power_on+0x163/0x4d0 net/bluetooth/hci_core.c:2211
 process_one_work+0x88b/0x1680 kernel/workqueue.c:2264
 worker_thread+0x85/0xb60 kernel/workqueue.c:2410
 kthread+0x331/0x3f0 kernel/kthread.c:255
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352