WARNING: locking bug in release_sock

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: c307aaf3eb47 Merge tag 'iommu-fixes-v4.19-rc5' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=134897fa400000
kernel config: https://syzkaller.appspot.com/x/.config?x=dfb440e26f0a6f6f
dashboard link: https://syzkaller.appspot.com/bug?extid=1c8d58c653c9e372dc1f
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [da...@davemloft.net kuz...@ms2.inr.ac.ru
linux-...@vger.kernel.org net...@vger.kernel.org yosh...@linux-ipv6.org]

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+1c8d58...@syzkaller.appspotmail.com

WARNING: CPU: 1 PID: 18775 at kernel/locking/lockdep.c:698
arch_local_save_flags arch/x86/include/asm/paravirt.h:783 [inline]
WARNING: CPU: 1 PID: 18775 at kernel/locking/lockdep.c:698
look_up_lock_class kernel/locking/lockdep.c:689 [inline]
WARNING: CPU: 1 PID: 18775 at kernel/locking/lockdep.c:698
register_lock_class+0xda2/0x29b0 kernel/locking/lockdep.c:748
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 18775 Comm: syz-executor2 Not tainted 4.19.0-rc5+ #256
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1c4/0x2b4 lib/dump_stack.c:113
panic+0x238/0x4e7 kernel/panic.c:184
__warn.cold.8+0x163/0x1ba kernel/panic.c:536
report_bug+0x254/0x2d0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
do_error_trap+0x1fc/0x4d0 arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:316
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:993
RIP: 0010:arch_local_save_flags arch/x86/include/asm/paravirt.h:783 [inline]
RIP: 0010:look_up_lock_class kernel/locking/lockdep.c:689 [inline]
RIP: 0010:register_lock_class+0xda2/0x29b0 kernel/locking/lockdep.c:748
Code: 68 fc ff ff 48 89 8d 70 fc ff ff e8 28 18 62 00 44 8b 8d 60 fc ff ff
44 8b 85 68 fc ff ff 48 8b 8d 70 fc ff ff e9 e0 f8 ff ff <0f> 0b e9 14 f6
ff ff 48 8d 70 01 48 69 c0 50 01 00 00 48 89 35 f5
RSP: 0018:ffff88018f6df250 EFLAGS: 00010083
RAX: 0000000000000004 RBX: ffffffff8b03de20 RCX: ffff8801b83cc7e0
RDX: ffffffff88c5dea0 RSI: 1ffffffff1698164 RDI: ffff8801b83cc7f8
RBP: ffff88018f6df660 R08: 0000000000000000 R09: 0000000000000000
R10: 1ffffffff1607bc8 R11: 0000000000000001 R12: 1ffff10031edbe5b
PM: Marking nosave pages: [mem 0x00000000-0x00000fff]
R13: 0000000000000003 R14: 0000000000000000 R15: ffffffff88dacf20
PM: Marking nosave pages: [mem 0x0009f000-0x000fffff]
__lock_acquire+0x1c1/0x4ec0 kernel/locking/lockdep.c:3299
PM: Marking nosave pages: [mem 0xbfffd000-0xffffffff]
lock_acquire+0x1ed/0x520 kernel/locking/lockdep.c:3900
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
_raw_spin_lock_bh+0x31/0x40 kernel/locking/spinlock.c:168
spin_lock_bh include/linux/spinlock.h:334 [inline]
release_sock+0x7d/0x2c0 net/core/sock.c:2847
ip6_datagram_connect+0x3a/0x50 net/ipv6/datagram.c:274
inet_dgram_connect+0x154/0x2e0 net/ipv4/af_inet.c:571
__sys_connect+0x37d/0x4c0 net/socket.c:1664
__do_sys_connect net/socket.c:1675 [inline]
__se_sys_connect net/socket.c:1672 [inline]
__x64_sys_connect+0x73/0xb0 net/socket.c:1672
do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457579
Code: 1d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 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 0f 83 eb b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007efed60a0c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002a
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000457579
RDX: 000000000000001c RSI: 0000000020000000 RDI: 0000000000000004
RBP: 000000000072bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007efed60a16d4
R13: 00000000004bda64 R14: 00000000004cc520 R15: 00000000ffffffff
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#bug-status-tracking for how to communicate with
syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.