WARNING: locking bug in inet_autobind (2)

6 views
Skip to first unread message

syzbot

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

syzbot found the following crash on:

HEAD commit: c10b57a5 Linux 4.14.176
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1794d210100000
kernel config: https://syzkaller.appspot.com/x/.config?x=457897b554d08537
dashboard link: https://syzkaller.appspot.com/bug?extid=a0a17bee35a410c2afc8
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+a0a17b...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 12098 at kernel/locking/lockdep.c:722 arch_local_save_flags arch/x86/include/asm/paravirt.h:774 [inline]
WARNING: CPU: 1 PID: 12098 at kernel/locking/lockdep.c:722 arch_local_save_flags arch/x86/include/asm/paravirt.h:772 [inline]
WARNING: CPU: 1 PID: 12098 at kernel/locking/lockdep.c:722 look_up_lock_class kernel/locking/lockdep.c:713 [inline]
WARNING: CPU: 1 PID: 12098 at kernel/locking/lockdep.c:722 register_lock_class+0xd7e/0x1600 kernel/locking/lockdep.c:756
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 12098 Comm: syz-executor.4 Not tainted 4.14.176-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
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x2f/0x30 kernel/panic.c:547
report_bug+0x20a/0x248 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:963
RIP: 0010:look_up_lock_class kernel/locking/lockdep.c:722 [inline]
RIP: 0010:register_lock_class+0xd7e/0x1600 kernel/locking/lockdep.c:756
RSP: 0018:ffff8880360dfa68 EFLAGS: 00010087
RAX: dffffc0000000000 RBX: ffffffff8a588b00 RCX: ffff88808eb4d8e0
RDX: 1ffff11011d69b1f RSI: 0000000000000000 RDI: ffff88808eb4d8f8
RBP: 1ffff11006c1bf57 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff8a0a1108 R11: 0000000000000000 R12: ffffffff8a114ee0
R13: ffffffff87381580 R14: 0000000000000000 R15: ffffffff8b0271b0
__lock_acquire+0x147/0x4620 kernel/locking/lockdep.c:3374
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3994
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
_raw_spin_lock_bh+0x2f/0x40 kernel/locking/spinlock.c:176
spin_lock_bh include/linux/spinlock.h:322 [inline]
lock_sock_nested+0x39/0x100 net/core/sock.c:2765
lock_sock include/net/sock.h:1467 [inline]
inet_autobind+0x1a/0x180 net/ipv4/af_inet.c:178
inet_dgram_connect+0x134/0x1f0 net/ipv4/af_inet.c:538
SYSC_connect+0x1c6/0x250 net/socket.c:1655
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x45c889
RSP: 002b:00007ff7fb1a6c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002a
RAX: ffffffffffffffda RBX: 00007ff7fb1a76d4 RCX: 000000000045c889
RDX: 000000000000001c RSI: 0000000020000040 RDI: 0000000000000006
RBP: 000000000076bfa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 0000000000000084 R14: 00000000004c320f R15: 000000000076bfac
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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,
Aug 15, 2020, 2:15:11 PM8/15/20
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages