[v6.6] BUG: MAX_LOCKDEP_KEYS too low!

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3a8ababb8b6a Linux 6.6.101
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=108586a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a2bd95b6de4839b7
dashboard link: https://syzkaller.appspot.com/bug?extid=f38657e44df302e426f0
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f06c672f5fa8/disk-3a8ababb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9af9b7afcdc5/vmlinux-3a8ababb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/351a55aafa77/bzImage-3a8ababb.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f38657...@syzkaller.appspotmail.com

BUG: MAX_LOCKDEP_KEYS too low!
turning off the locking correctness validator.
CPU: 0 PID: 59 Comm: kworker/u4:4 Not tainted 6.6.101-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Workqueue: events_unbound linkwatch_event
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
register_lock_class+0x6c0/0x890 kernel/locking/lockdep.c:1321
__lock_acquire+0x17a/0x7c80 kernel/locking/lockdep.c:5014
lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline]
_raw_spin_lock_bh+0x36/0x50 kernel/locking/spinlock.c:178
spin_lock_bh include/linux/spinlock.h:356 [inline]
dev_reset_queue+0xfa/0x1a0 net/sched/sch_generic.c:1305
netdev_for_each_tx_queue include/linux/netdevice.h:2520 [inline]
dev_deactivate_many+0x6c5/0xcb0 net/sched/sch_generic.c:1373
dev_deactivate+0x110/0x1a0 net/sched/sch_generic.c:1396
linkwatch_do_dev+0x105/0x160 net/core/link_watch.c:189
__linkwatch_run_queue+0x40f/0x660 net/core/link_watch.c:244
linkwatch_event+0x4c/0x60 net/core/link_watch.c:287
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 3a8ababb8b6a Linux 6.6.101
git tree: linux-6.6.y

console output: https://syzkaller.appspot.com/x/log.txt?x=121ae042580000

kernel config: https://syzkaller.appspot.com/x/.config?x=a2bd95b6de4839b7
dashboard link: https://syzkaller.appspot.com/bug?extid=f38657e44df302e426f0
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1770f6a2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12c84ea2580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f06c672f5fa8/disk-3a8ababb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9af9b7afcdc5/vmlinux-3a8ababb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/351a55aafa77/bzImage-3a8ababb.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f38657...@syzkaller.appspotmail.com

BUG: MAX_LOCKDEP_KEYS too low!
turning off the locking correctness validator.

CPU: 0 PID: 58 Comm: kworker/u4:4 Not tainted 6.6.101-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025

Workqueue: bond366 bond_alb_monitor

Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
register_lock_class+0x6c0/0x890 kernel/locking/lockdep.c:1321
__lock_acquire+0x17a/0x7c80 kernel/locking/lockdep.c:5014
lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754

process_one_work kernel/workqueue.c:2609 [inline]
process_scheduled_works+0x96d/0x15b0 kernel/workqueue.c:2711

worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>


---

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.