syzbot has found a reproducer for the following issue on: HEAD commit: 6f513529296f Merge tag 'for-5.16-rc4-tag' of git://git.ker.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10a8954db00000 kernel config: https://syzkaller.appspot.com/x/.config?x=221ffc09e39ebbd1 dashboard link: https://syzkaller.appspot.com/bug?extid=8a249628ae32ea7de3a2 compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12777551b00000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15a99a05b00000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+8a249628ae32ea7de3a2@xxxxxxxxxxxxxxxxxxxxxxxxx BUG: MAX_LOCKDEP_CHAINS too low! turning off the locking correctness validator. CPU: 0 PID: 6709 Comm: kworker/u4:7 Not tainted 5.16.0-rc4-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: bond1948 bond_netdev_notify_work Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 add_chain_cache kernel/locking/lockdep.c:3649 [inline] lookup_chain_cache_add kernel/locking/lockdep.c:3748 [inline] validate_chain kernel/locking/lockdep.c:3769 [inline] __lock_acquire.cold+0x372/0x3ab kernel/locking/lockdep.c:5027 lock_acquire kernel/locking/lockdep.c:5637 [inline] lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5602 process_one_work+0x921/0x1690 kernel/workqueue.c:2274 worker_thread+0x658/0x11f0 kernel/workqueue.c:2445 kthread+0x405/0x4f0 kernel/kthread.c:327 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 </TASK>
