WARNING in enter_vmx_operation

[syzbot <syzbot+ab5d7a5d0fc0c7518f6d@syzkaller.appspotmail.com>]

Hello,

syzbot found the following crash on:

HEAD commit:    3f16503b7d22 Merge branch 'fixes' of git://git.kernel.org/..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16c7df6a400000
kernel config:  https://syzkaller.appspot.com/x/.config?x=49927b422dcf0b29
dashboard link: https://syzkaller.appspot.com/bug?extid=ab5d7a5d0fc0c7518f6d
compiler:       gcc (GCC) 8.0.1 20180413 (experimental)
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=132365a6400000

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

IPv6: ADDRCONF(NETDEV_UP): veth1: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
8021q: adding VLAN 0 to HW filter on device team0
L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and  
https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html for details.
WARNING: CPU: 1 PID: 4748 at arch/x86/kvm/vmx.c:8247 alloc_shadow_vmcs  
arch/x86/kvm/vmx.c:8247 [inline]
WARNING: CPU: 1 PID: 4748 at arch/x86/kvm/vmx.c:8247  
enter_vmx_operation+0x391/0x470 arch/x86/kvm/vmx.c:8274
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 4748 Comm: syz-executor0 Not tainted 4.19.0-rc1+ #213
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+0x1c9/0x2b4 lib/dump_stack.c:113
  panic+0x238/0x4e7 kernel/panic.c:184
  __warn.cold.8+0x163/0x1ba kernel/panic.c:536
  report_bug+0x252/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:alloc_shadow_vmcs arch/x86/kvm/vmx.c:8247 [inline]
RIP: 0010:enter_vmx_operation+0x391/0x470 arch/x86/kvm/vmx.c:8274
Code: 00 4c 89 ef bb f4 ff ff ff e8 7b ec ff ff e9 f2 fe ff ff e8 71 dc 5f  
00 48 8b 4d d0 48 85 c9 0f 84 08 ff ff ff e8 5f dc 5f 00 <0f> 0b e9 0e fe  
ff ff e8 f3 d9 9e 00 e9 c1 fe ff ff e8 09 da 9e 00
RSP: 0018:ffff8801aa826f48 EFLAGS: 00010293
RAX: ffff8801abbde080 RBX: ffff8801d3668040 RCX: ffff8801c366d000
RDX: 0000000000000000 RSI: ffffffff811ce421 RDI: ffff8801d366d820
RBP: ffff8801aa826f80 R08: ffff8801abbde080 R09: ffffed003b6246de
R10: ffffed003b6246de R11: ffff8801db1236f3 R12: ffff8801d366dba8
R13: ffff8801d366dbb8 R14: ffff8801d366dba0 R15: ffff8801d366d7a8
  vmx_set_nested_state+0x4d6/0xea0 arch/x86/kvm/vmx.c:13944
  kvm_arch_vcpu_ioctl+0x790/0x3ac0 arch/x86/kvm/x86.c:4048
  kvm_vcpu_ioctl+0x286/0x1280 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2742
  vfs_ioctl fs/ioctl.c:46 [inline]
  file_ioctl fs/ioctl.c:501 [inline]
  do_vfs_ioctl+0x1de/0x1720 fs/ioctl.c:685
  ksys_ioctl+0xa9/0xd0 fs/ioctl.c:702
  __do_sys_ioctl fs/ioctl.c:709 [inline]
  __se_sys_ioctl fs/ioctl.c:707 [inline]
  __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:707
  do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
  entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457089
Code: fd 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 cb b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f0ac2b1cc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f0ac2b1d6d4 RCX: 0000000000457089
RDX: 0000000020000580 RSI: 000000004080aebf RDI: 0000000000000005
RBP: 0000000000930140 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000004cf070 R14: 00000000004c56c3 R15: 0000000000000001
Dumping ftrace buffer:
    (ftrace buffer empty)
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 syzkaller@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 can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches