[v6.1] BUG: MAX_LOCKDEP_ENTRIES too low!

8 views
Skip to first unread message

syzbot

unread,
Aug 21, 2023, 5:06:27 AM8/21/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 6c44e13dc284 Linux 6.1.46
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=108cbd07a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d53bfb03cd3f0d5d
dashboard link: https://syzkaller.appspot.com/bug?extid=716f924b26ffcefa3bed
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e2aebba80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14fb1defa80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/706045968752/disk-6c44e13d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2f25349b69b4/vmlinux-6c44e13d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e6791616e516/bzImage-6c44e13d.xz

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

netlink: 4 bytes leftover after parsing attributes in process `syz-executor338'.
BUG: MAX_LOCKDEP_ENTRIES too low!
turning off the locking correctness validator.
CPU: 0 PID: 4865 Comm: syz-executor338 Not tainted 6.1.46-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/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:1403 [inline]
add_lock_to_list+0x81/0x2e0 kernel/locking/lockdep.c:1424
check_prev_add kernel/locking/lockdep.c:3168 [inline]
check_prevs_add kernel/locking/lockdep.c:3217 [inline]
validate_chain+0x2c23/0x58e0 kernel/locking/lockdep.c:3832
__lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
__raw_read_lock_bh include/linux/rwlock_api_smp.h:176 [inline]
_raw_read_lock_bh+0x39/0x50 kernel/locking/spinlock.c:252
lapb_devtostruct net/lapb/lapb_iface.c:102 [inline]
lapb_device_event+0xac/0x630 net/lapb/lapb_iface.c:467
notifier_call_chain kernel/notifier.c:87 [inline]
raw_notifier_call_chain+0xd0/0x170 kernel/notifier.c:455
call_netdevice_notifiers_info net/core/dev.c:1945 [inline]
call_netdevice_notifiers_extack net/core/dev.c:1983 [inline]
call_netdevice_notifiers net/core/dev.c:1997 [inline]
register_netdevice+0x101a/0x1700 net/core/dev.c:10059
lapbeth_new_device drivers/net/wan/lapbether.c:418 [inline]
lapbeth_device_event+0x75e/0x9e0 drivers/net/wan/lapbether.c:460
notifier_call_chain kernel/notifier.c:87 [inline]
raw_notifier_call_chain+0xd0/0x170 kernel/notifier.c:455
call_netdevice_notifiers_info net/core/dev.c:1945 [inline]
call_netdevice_notifiers_extack net/core/dev.c:1983 [inline]
call_netdevice_notifiers net/core/dev.c:1997 [inline]
dev_open+0x1c1/0x260 net/core/dev.c:1473
team_port_add drivers/net/team/team.c:1215 [inline]
team_add_slave+0x932/0x2710 drivers/net/team/team.c:1985
do_set_master net/core/rtnetlink.c:2584 [inline]
rtnl_newlink_create net/core/rtnetlink.c:3393 [inline]
__rtnl_newlink net/core/rtnetlink.c:3593 [inline]
rtnl_newlink+0x1ae7/0x1fa0 net/core/rtnetlink.c:3606
rtnetlink_rcv_msg+0x776/0xf00 net/core/rtnetlink.c:6107
netlink_rcv_skb+0x1cd/0x410 net/netlink/af_netlink.c:2525
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:1903
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:0x7f76cd6e6c19
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 71 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:00007ffe2933ea08 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f76cd6e6c19
RDX: 0000000000000000 RSI: 0000000020000300 RDI: 0000000000000005
RBP: 0000000000000000 R08: 0000000000000006 R09: 0000000000000006
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001
</TASK>
8021q: adding VLAN 0 to HW filter on device batadv977
team977: Port device batadv977 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 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.

If you want to overwrite 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
Reply all
Reply to author
Forward
0 new messages