BUG: looking up invalid subclass: 8

8 views
Skip to first unread message

syzbot

unread,
Apr 3, 2020, 2:19:14 PM4/3/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 4520f06b Linux 4.14.175
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=172f3b1fe00000
kernel config: https://syzkaller.appspot.com/x/.config?x=93cf891381c0c347
dashboard link: https://syzkaller.appspot.com/bug?extid=37784afd3fb205ca5611
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

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

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

BUG: looking up invalid subclass: 8
turning off the locking correctness validator.
CPU: 1 PID: 9061 Comm: syz-executor.0 Not tainted 4.14.175-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x13e/0x194 lib/dump_stack.c:58
look_up_lock_class kernel/locking/lockdep.c:673 [inline]
register_lock_class+0x4cf/0x1600 kernel/locking/lockdep.c:756
__lockdep_init_map+0x2a7/0x560 kernel/locking/lockdep.c:3273
vlan_dev_set_lockdep_class net/8021q/vlan_dev.c:509 [inline]
vlan_dev_init+0x78a/0xc00 net/8021q/vlan_dev.c:604
register_netdevice+0x286/0xc70 net/core/dev.c:7590
register_vlan_dev+0x28d/0x6a0 net/8021q/vlan.c:168
vlan_newlink+0x3b9/0x510 net/8021q/vlan_netlink.c:165
rtnl_newlink+0xecb/0x1720 net/core/rtnetlink.c:2728
rtnetlink_rcv_msg+0x3be/0xb10 net/core/rtnetlink.c:4315
netlink_rcv_skb+0x127/0x370 net/netlink/af_netlink.c:2433
netlink_unicast_kernel net/netlink/af_netlink.c:1287 [inline]
netlink_unicast+0x437/0x620 net/netlink/af_netlink.c:1313
netlink_sendmsg+0x733/0xbe0 net/netlink/af_netlink.c:1878
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xc5/0x100 net/socket.c:656
___sys_sendmsg+0x70a/0x840 net/socket.c:2062
__sys_sendmsg+0xa3/0x120 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x27/0x40 net/socket.c:2103
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x45c849
RSP: 002b:00007fe5e7dd3c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007fe5e7dd46d4 RCX: 000000000045c849
RDX: 0000000000000000 RSI: 0000000020000140 RDI: 0000000000000004
audit: type=1804 audit(1585937894.342:16): pid=9074 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir747015134/syzkaller.S81Tkd/21/bus" dev="sda1" ino=15858 res=1
RBP: 000000000076bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000000009fc R14: 00000000004ccb3c R15: 000000000076bf0c
audit: type=1804 audit(1585937894.702:17): pid=9072 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="ToMToU" comm="syz-executor.5" name="/root/syzkaller-testdir747015134/syzkaller.S81Tkd/21/bus" dev="sda1" ino=15858 res=1
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns
kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
NOHZ: local_softirq_pending 08
NOHZ: local_softirq_pending 08
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Apr 3, 2020, 3:13:16 PM4/3/20
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following crash on:

HEAD commit: 4520f06b Linux 4.14.175
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1509a4b3e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=93cf891381c0c347
dashboard link: https://syzkaller.appspot.com/bug?extid=37784afd3fb205ca5611
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15127db7e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=120af42be00000

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

BUG: looking up invalid subclass: 8
turning off the locking correctness validator.
CPU: 1 PID: 7403 Comm: syz-executor679 Not tainted 4.14.175-syzkaller #0
RIP: 0033:0x4494f9
RSP: 002b:00007fcfeda35d98 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00000000006dec48 RCX: 00000000004494f9
RDX: 0000000000000000 RSI: 0000000020000140 RDI: 0000000000000004
RBP: 00000000006dec40 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000006dec4c
R13: 0000000000000000 R14: 0000000000000000 R15: 0565001000000050
Dead loop on virtual device veth0_vlan, fix it urgently!
Dead loop on virtual device veth0_vlan, fix it urgently!
Dead loop on virtual device veth1_vlan, fix it urgently!
Dead loop on virtual device veth1_vlan, fix it urgently!
Dead loop on virtual device veth1_vlan, fix it urgently!
Dead loop on virtual device veth0_vlan, fix it urgently!
Dead loop on virtual device veth0_vlan, fix it urgently!
Dead loop on virtual device team0, fix it urgently!
Dead loop on virtual device team0, fix it urgently!
Dead loop on virtual device veth0, fix it urgently!
net_ratelimit: 1400 callbacks suppressed
Dead loop on virtual device veth0_to_bond, fix it urgently!
Dead loop on virtual device veth0_to_team, fix it urgently!
Dead loop on virtual device veth0_to_bridge, fix it urgently!
Dead loop on virtual device vlan70, fix it urgently!
Dead loop on virtual device vlan36, fix it urgently!
Dead loop on virtual device vlan88, fix it urgently!
Dead loop on virtual device vlan35, fix it urgently!
Dead loop on virtual device vlan68, fix it urgently!
Dead loop on virtual device veth0_to_hsr, fix it urgently!
Dead loop on virtual device vlan118, fix it urgently!

Reply all
Reply to author
Forward
0 new messages