[v6.1] BUG: MAX_LOCKDEP_KEYS too low!

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 543aff194ab6 Linux 6.1.23
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1340b5fdc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e9affea290775ea7
dashboard link: https://syzkaller.appspot.com/bug?extid=0752173038063aaf3f0f
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6fe9097a8f09/disk-543aff19.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9df5aa0f6266/vmlinux-543aff19.xz
kernel image: https://storage.googleapis.com/syzbot-assets/84127c4bde2b/bzImage-543aff19.xz

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

BUG: MAX_LOCKDEP_KEYS too low!
turning off the locking correctness validator.
CPU: 0 PID: 9352 Comm: syz-executor.1 Not tainted 6.1.23-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
register_lock_class+0x83d/0x990 kernel/locking/lockdep.c:1327
__lock_acquire+0xd3/0x1f80 kernel/locking/lockdep.c:4935
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
__flush_workqueue+0x170/0x1610 kernel/workqueue.c:2809
drain_workqueue+0xc5/0x390 kernel/workqueue.c:2974
destroy_workqueue+0x7b/0xae0 kernel/workqueue.c:4420
alloc_workqueue+0x117d/0x1440 kernel/workqueue.c:4381
bond_init+0xc1/0x740 drivers/net/bonding/bond_main.c:6281
register_netdevice+0x5c3/0x1700 net/core/dev.c:9989
bond_newlink+0x37/0x80 drivers/net/bonding/bond_netlink.c:560
rtnl_newlink_create net/core/rtnetlink.c:3364 [inline]
__rtnl_newlink net/core/rtnetlink.c:3581 [inline]
rtnl_newlink+0x1438/0x1fa0 net/core/rtnetlink.c:3594
rtnetlink_rcv_msg+0x776/0xf00 net/core/rtnetlink.c:6091
netlink_rcv_skb+0x1cd/0x410 net/netlink/af_netlink.c:2550
netlink_unicast_kernel net/netlink/af_netlink.c:1328 [inline]
netlink_unicast+0x7bf/0x990 net/netlink/af_netlink.c:1354
netlink_sendmsg+0xa26/0xd60 net/netlink/af_netlink.c:1931
sock_sendmsg_nosec net/socket.c:716 [inline]
sock_sendmsg net/socket.c:736 [inline]
____sys_sendmsg+0x59e/0x8f0 net/socket.c:2482
___sys_sendmsg net/socket.c:2536 [inline]
__sys_sendmsg+0x2a9/0x390 net/socket.c:2565
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f464048c169
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f4641117168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f46405ac120 RCX: 00007f464048c169
RDX: 0000000000000000 RSI: 0000000020000040 RDI: 0000000000000005
RBP: 00007f46404e7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd335056bf R14: 00007f4641117300 R15: 0000000000022000
</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.

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: bf4ad6fa4e53 Linux 6.1.28
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13b2b2c2280000
kernel config: https://syzkaller.appspot.com/x/.config?x=26fca33e75c97e43

dashboard link: https://syzkaller.appspot.com/bug?extid=0752173038063aaf3f0f
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=110420fa280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13ad764e280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/058ee41df9de/disk-bf4ad6fa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/480706160d27/vmlinux-bf4ad6fa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e6a9f4f20a23/bzImage-bf4ad6fa.xz

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

device team1089 entered promiscuous mode
8021q: adding VLAN 0 to HW filter on device team1089

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

CPU: 1 PID: 10146 Comm: syz-executor347 Not tainted 6.1.28-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023

Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
register_lock_class+0x83d/0x990 kernel/locking/lockdep.c:1327
__lock_acquire+0xd3/0x1f80 kernel/locking/lockdep.c:4935
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669

__mutex_lock_common+0x1d4/0x2520 kernel/locking/mutex.c:603
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
team_vlan_rx_add_vid+0x33/0x140 drivers/net/team/team.c:1904
vlan_add_rx_filter_info net/8021q/vlan_core.c:211 [inline]
__vlan_vid_add net/8021q/vlan_core.c:306 [inline]
vlan_vid_add+0x643/0x740 net/8021q/vlan_core.c:336
vlan_device_event+0x1c11/0x1d10 net/8021q/vlan.c:385
notifier_call_chain kernel/notifier.c:87 [inline]
raw_notifier_call_chain+0xd0/0x170 kernel/notifier.c:455
__dev_notify_flags+0x304/0x610
rtnl_newlink_create net/core/rtnetlink.c:3372 [inline]
__rtnl_newlink net/core/rtnetlink.c:3581 [inline]
rtnl_newlink+0x194a/0x1fa0 net/core/rtnetlink.c:3594
rtnetlink_rcv_msg+0x776/0xf00 net/core/rtnetlink.c:6091
netlink_rcv_skb+0x1cd/0x410 net/netlink/af_netlink.c:2524

netlink_unicast_kernel net/netlink/af_netlink.c:1328 [inline]
netlink_unicast+0x7bf/0x990 net/netlink/af_netlink.c:1354

netlink_sendmsg+0xa26/0xd60 net/netlink/af_netlink.c:1902

sock_sendmsg_nosec net/socket.c:716 [inline]
sock_sendmsg net/socket.c:736 [inline]
____sys_sendmsg+0x59e/0x8f0 net/socket.c:2482
___sys_sendmsg net/socket.c:2536 [inline]
__sys_sendmsg+0x2a9/0x390 net/socket.c:2565
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd

RIP: 0033:0x7fb59ef8c329
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 11 15 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff4cd48338 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fb59ef8c329
RDX: 0000000000000000 RSI: 0000000020000040 RDI: 0000000000000003
RBP: 0000000000000000 R08: 000000009eff9e40 R09: 000000009eff9e40
R10: 000000009eff9e40 R11: 0000000000000246 R12: 00000000000c78ee
R13: 00007fff4cd48360 R14: 00007fff4cd48350 R15: 00007fff4cd48344
</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.