[v5.15] BUG: MAX_LOCKDEP_ENTRIES too low!

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b0ece631f84a Linux 5.15.111
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13179e16280000
kernel config: https://syzkaller.appspot.com/x/.config?x=5e93479ceb1e500
dashboard link: https://syzkaller.appspot.com/bug?extid=bade942b7519fb0b7a00
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/4dbb092b5601/disk-b0ece631.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5fe7e3edcf9b/vmlinux-b0ece631.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b2e75f47bfb/bzImage-b0ece631.xz

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

BUG: MAX_LOCKDEP_ENTRIES too low!
turning off the locking correctness validator.
CPU: 1 PID: 12041 Comm: syz-executor.4 Not tainted 5.15.111-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
alloc_list_entry kernel/locking/lockdep.c:1358 [inline]
add_lock_to_list+0x280/0x2d0 kernel/locking/lockdep.c:1379
check_prev_add kernel/locking/lockdep.c:3123 [inline]
check_prevs_add kernel/locking/lockdep.c:3172 [inline]
validate_chain+0x2c1d/0x58b0 kernel/locking/lockdep.c:3787
__lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5011
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
_raw_spin_lock_bh+0x31/0x40 kernel/locking/spinlock.c:178
spin_lock_bh include/linux/spinlock.h:368 [inline]
igmpv3_del_delrec+0x8e/0x710 net/ipv4/igmp.c:1221
____ip_mc_inc_group+0x98c/0xbf0 net/ipv4/igmp.c:1473
__ip_mc_inc_group net/ipv4/igmp.c:1484 [inline]
ip_mc_inc_group net/ipv4/igmp.c:1490 [inline]
ip_mc_up+0x11b/0x2f0 net/ipv4/igmp.c:1789
inetdev_event+0xf24/0x1490 net/ipv4/devinet.c:1573
notifier_call_chain kernel/notifier.c:83 [inline]
raw_notifier_call_chain+0xd0/0x170 kernel/notifier.c:391
call_netdevice_notifiers_info net/core/dev.c:1998 [inline]
call_netdevice_notifiers_extack net/core/dev.c:2010 [inline]
call_netdevice_notifiers net/core/dev.c:2024 [inline]
dev_open+0x1c1/0x260 net/core/dev.c:1527
team_port_add drivers/net/team/team.c:1210 [inline]
team_add_slave+0x916/0x2760 drivers/net/team/team.c:1979
do_set_master net/core/rtnetlink.c:2523 [inline]
__rtnl_newlink net/core/rtnetlink.c:3479 [inline]
rtnl_newlink+0x1b68/0x2060 net/core/rtnetlink.c:3510
rtnetlink_rcv_msg+0x993/0xee0 net/core/rtnetlink.c:5587
netlink_rcv_skb+0x1cf/0x410 net/netlink/af_netlink.c:2504
netlink_unicast_kernel net/netlink/af_netlink.c:1330 [inline]
netlink_unicast+0x7b6/0x980 net/netlink/af_netlink.c:1356
netlink_sendmsg+0xa30/0xd60 net/netlink/af_netlink.c:1923
sock_sendmsg_nosec net/socket.c:704 [inline]
sock_sendmsg net/socket.c:724 [inline]
____sys_sendmsg+0x59e/0x8f0 net/socket.c:2412
___sys_sendmsg+0x252/0x2e0 net/socket.c:2466
__sys_sendmsg net/socket.c:2495 [inline]
__do_sys_sendmsg net/socket.c:2504 [inline]
__se_sys_sendmsg+0x19a/0x260 net/socket.c:2502
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+0x61/0xcb
RIP: 0033:0x7f4f76529169
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:00007f4f74a59168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f4f76649120 RCX: 00007f4f76529169
RDX: 0000000000000000 RSI: 0000000020000300 RDI: 0000000000000005
RBP: 00007f4f76584ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd309016bf R14: 00007f4f74a59300 R15: 0000000000022000
</TASK>
8021q: adding VLAN 0 to HW filter on device macvlan554
team636: Port device macvlan554 added


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

If the bug is a duplicate of another bug, 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: 7349e40704a0 Linux 5.15.116
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12e0bc07280000
kernel config: https://syzkaller.appspot.com/x/.config?x=831c3122ac9c9145

dashboard link: https://syzkaller.appspot.com/bug?extid=bade942b7519fb0b7a00
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=1525a1dd280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=127d352d280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8c03c3ad4501/disk-7349e407.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/350c3d79bc87/vmlinux-7349e407.xz
kernel image: https://storage.googleapis.com/syzbot-assets/73a4ed3d5438/bzImage-7349e407.xz

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

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

CPU: 0 PID: 4868 Comm: syz-executor123 Not tainted 5.15.116-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023

Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
alloc_list_entry kernel/locking/lockdep.c:1358 [inline]
add_lock_to_list+0x280/0x2d0 kernel/locking/lockdep.c:1379
check_prev_add kernel/locking/lockdep.c:3123 [inline]
check_prevs_add kernel/locking/lockdep.c:3172 [inline]
validate_chain+0x2c1d/0x58b0 kernel/locking/lockdep.c:3787
__lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5011
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622

__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0xd1/0x120 kernel/locking/spinlock.c:162
complete_all+0x14/0x70 kernel/sched/completion.c:63
device_pm_sleep_init+0x80/0x130 drivers/base/power/main.c:105
device_pm_init drivers/base/power/power.h:164 [inline]
device_initialize+0x25c/0x4d0 drivers/base/core.c:2875
netdev_register_kobject+0x2f/0x310 net/core/net-sysfs.c:1990
register_netdevice+0x1067/0x1700 net/core/dev.c:10329
bpq_new_device drivers/net/hamradio/bpqether.c:500 [inline]
bpq_device_event+0x4d6/0x9d0 drivers/net/hamradio/bpqether.c:543

notifier_call_chain kernel/notifier.c:83 [inline]
raw_notifier_call_chain+0xd0/0x170 kernel/notifier.c:391
call_netdevice_notifiers_info net/core/dev.c:1998 [inline]
call_netdevice_notifiers_extack net/core/dev.c:2010 [inline]
call_netdevice_notifiers net/core/dev.c:2024 [inline]
dev_open+0x1c1/0x260 net/core/dev.c:1527
team_port_add drivers/net/team/team.c:1210 [inline]

team_add_slave+0x916/0x2760 drivers/net/team/team.c:1980
do_set_master net/core/rtnetlink.c:2523 [inline]
__rtnl_newlink net/core/rtnetlink.c:3485 [inline]
rtnl_newlink+0x1b68/0x2060 net/core/rtnetlink.c:3516
rtnetlink_rcv_msg+0x993/0xee0 net/core/rtnetlink.c:5593

netlink_rcv_skb+0x1cf/0x410 net/netlink/af_netlink.c:2504
netlink_unicast_kernel net/netlink/af_netlink.c:1330 [inline]
netlink_unicast+0x7b6/0x980 net/netlink/af_netlink.c:1356
netlink_sendmsg+0xa30/0xd60 net/netlink/af_netlink.c:1923
sock_sendmsg_nosec net/socket.c:704 [inline]
sock_sendmsg net/socket.c:724 [inline]
____sys_sendmsg+0x59e/0x8f0 net/socket.c:2412
___sys_sendmsg+0x252/0x2e0 net/socket.c:2466
__sys_sendmsg net/socket.c:2495 [inline]
__do_sys_sendmsg net/socket.c:2504 [inline]
__se_sys_sendmsg+0x19a/0x260 net/socket.c:2502
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+0x61/0xcb

RIP: 0033:0x7f74e188cac9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 14 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:00007ffc4524b848 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 000000000006a4ac RCX: 00007f74e188cac9

RDX: 0000000000000000 RSI: 0000000020000300 RDI: 0000000000000005

RBP: 0000000000000000 R08: 00007ffc4524b9e8 R09: 00007ffc4524b9e8
R10: 00007ffc4524b9e8 R11: 0000000000000246 R12: 00007ffc4524b85c
R13: 431bde82d7b634db R14: 0000000000000000 R15: 0000000000000000
</TASK>
8021q: adding VLAN 0 to HW filter on device batadv968
team968: Port device batadv968 added


---
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.

[syzbot]

syzbot suspects this issue could be fixed by backporting the following commit:

commit 425b9c7f51c98443db71ad679893725483b21196
git tree: upstream
Author: Vasily Averin <v...@openvz.org>
Date: Mon May 2 12:15:51 2022 +0000

memcg: accounting for objects allocated for new netdevice

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15d8851c680000

kernel config: https://syzkaller.appspot.com/x/.config?x=831c3122ac9c9145
dashboard link: https://syzkaller.appspot.com/bug?extid=bade942b7519fb0b7a00

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1525a1dd280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=127d352d280000

Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection