WARNING: locking bug in lock_sock_nested

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: fa5941f4 Linux 4.14.114
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=103e9d14a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=d7780000df8e070e
dashboard link: https://syzkaller.appspot.com/bug?extid=484d48a66e9695604115
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1033e2b8a00000

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

IPv6: ADDRCONF(NETDEV_CHANGE): team0: link becomes ready
IPv6: ADDRCONF(NETDEV_UP): vxcan1: link is not ready
8021q: adding VLAN 0 to HW filter on device batadv0
IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
------------[ cut here ]------------
WARNING: CPU: 0 PID: 7255 at kernel/locking/lockdep.c:722
arch_local_save_flags arch/x86/include/asm/paravirt.h:773 [inline]
WARNING: CPU: 0 PID: 7255 at kernel/locking/lockdep.c:722
arch_local_save_flags arch/x86/include/asm/paravirt.h:771 [inline]
WARNING: CPU: 0 PID: 7255 at kernel/locking/lockdep.c:722
look_up_lock_class kernel/locking/lockdep.c:713 [inline]
WARNING: CPU: 0 PID: 7255 at kernel/locking/lockdep.c:722
register_lock_class+0xd80/0x1730 kernel/locking/lockdep.c:756
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 7255 Comm: syz-executor.0 Not tainted 4.14.114 #4
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+0x138/0x19c lib/dump_stack.c:53
panic+0x1f2/0x438 kernel/panic.c:182
__warn.cold+0x2f/0x34 kernel/panic.c:546
report_bug+0x216/0x254 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+0x1bb/0x310 arch/x86/kernel/traps.c:295
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:314
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:944
RIP: 0010:look_up_lock_class kernel/locking/lockdep.c:722 [inline]
RIP: 0010:register_lock_class+0xd80/0x1730 kernel/locking/lockdep.c:756
RSP: 0018:ffff8880a6fb7a00 EFLAGS: 00010083
RAX: dffffc0000000000 RBX: ffffffff891a5680 RCX: ffff8880903c11e0
RDX: 1ffff1101207823f RSI: 1ffffffff11a4f4c RDI: ffff8880903c11f8
RBP: ffff8880a6fb7ac0 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff88cbff90 R11: 0000000000000000 R12: ffffffff88d27a40
R13: 1ffff11014df6f4b R14: ffffffff86ee83c0 R15: 0000000000000000
__lock_acquire+0x147/0x45e0 kernel/locking/lockdep.c:3374
lock_acquire+0x16f/0x430 kernel/locking/lockdep.c:3991
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
_raw_spin_lock_bh+0x33/0x50 kernel/locking/spinlock.c:176
spin_lock_bh include/linux/spinlock.h:322 [inline]
lock_sock_nested+0x3f/0x110 net/core/sock.c:2760
lock_sock include/net/sock.h:1462 [inline]
inet_autobind+0x20/0x190 net/ipv4/af_inet.c:178
inet_dgram_connect+0x13b/0x1f0 net/ipv4/af_inet.c:538
SYSC_connect+0x1f8/0x2d0 net/socket.c:1655
SyS_connect+0x24/0x30 net/socket.c:1636
do_syscall_64+0x1eb/0x630 arch/x86/entry/common.c:289
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x458da9
RSP: 002b:00007f2e662ccc78 EFLAGS: 00000246 ORIG_RAX: 000000000000002a
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000458da9
RDX: 000000000000001c RSI: 0000000020000080 RDI: 0000000000000008
RBP: 000000000073bfa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f2e662cd6d4
R13: 00000000004bf1f1 R14: 00000000004d02c0 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#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches