syzbot

BUG: MAX_LOCKDEP_KEYS too low!
turning off the locking correctness validator.
CPU: 0 UID: 0 PID: 5074 Comm: syz-executor291 Not tainted 6.15.0-rc5-syzkaller-00353-gcd802e7e5f1e #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 register_lock_class+0x2e8/0x320 kernel/locking/lockdep.c:1333
 __lock_acquire+0x7f/0xd20 kernel/locking/lockdep.c:5110
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866
 touch_wq_lockdep_map+0xcb/0x180 kernel/workqueue.c:3907
 __flush_workqueue+0x121/0x14b0 kernel/workqueue.c:3949
 drain_workqueue+0xd3/0x390 kernel/workqueue.c:4113
 destroy_workqueue+0xbb/0xc70 kernel/workqueue.c:5858
 nci_unregister_device+0xb1/0x240 net/nfc/nci/core.c:1316
 virtual_ncidev_close+0x56/0x90 drivers/nfc/virtual_ncidev.c:172
 __fput+0x449/0xa70 fs/file_table.c:465
 task_work_run+0x1d1/0x260 kernel/task_work.c:227
 exit_task_work include/linux/task_work.h:40 [inline]
 do_exit+0x8d6/0x2550 kernel/exit.c:953
 do_group_exit+0x21c/0x2d0 kernel/exit.c:1102
 __do_sys_exit_group kernel/exit.c:1113 [inline]
 __se_sys_exit_group kernel/exit.c:1111 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1111
 x64_sys_call+0x21ba/0x21c0 arch/x86/include/generated/asm/syscalls_64.h:232
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7faa947c7c39
Code: Unable to access opcode bytes at 0x7faa947c7c0f.
RSP: 002b:00007fffd7b7c518 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007faa947c7c39
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 00007faa94842290 R08: ffffffffffffffb8 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007faa94842290
R13: 0000000000000000 R14: 00007faa94842d00 R15: 00007faa94798dd0
 </TASK>