KCSAN: data-race in direct_page_fault / kvm_set_memslot (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b3298500 Merge tag 'for-5.10/dm-fixes' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1589d8df500000
kernel config: https://syzkaller.appspot.com/x/.config?x=c949fed53798f819
dashboard link: https://syzkaller.appspot.com/bug?extid=bd01b6d8ba4d4d5ec9e2
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project.git 913f6005669cfb590c99865a90bc51ed0983d09d)
CC: [k...@vger.kernel.org linux-...@vger.kernel.org pbon...@redhat.com]

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

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

==================================================================
BUG: KCSAN: data-race in direct_page_fault / kvm_set_memslot

write to 0xffff88801416e000 of 8 bytes by task 22474 on cpu 0:
install_new_memslots arch/x86/kvm/../../../virt/kvm/kvm_main.c:1146 [inline]
kvm_set_memslot+0x945/0xa00 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1222
__kvm_set_memory_region+0x708/0x910 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1374
kvm_set_memory_region arch/x86/kvm/../../../virt/kvm/kvm_main.c:1395 [inline]
kvm_vm_ioctl_set_memory_region arch/x86/kvm/../../../virt/kvm/kvm_main.c:1407 [inline]
kvm_vm_ioctl+0x822/0x17d0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3708
vfs_ioctl fs/ioctl.c:48 [inline]
__do_sys_ioctl fs/ioctl.c:753 [inline]
__se_sys_ioctl+0xcb/0x140 fs/ioctl.c:739
__x64_sys_ioctl+0x3f/0x50 fs/ioctl.c:739
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9

read to 0xffff88801416e000 of 8 bytes by task 22438 on cpu 1:
vcpu_cache_mmio_info arch/x86/kvm/x86.h:172 [inline]
handle_abnormal_pfn arch/x86/kvm/mmu/mmu.c:2952 [inline]
direct_page_fault+0x491/0x770 arch/x86/kvm/mmu/mmu.c:3708
kvm_tdp_page_fault+0x92/0xa0 arch/x86/kvm/mmu/mmu.c:3790
kvm_mmu_do_page_fault arch/x86/kvm/mmu.h:112 [inline]
kvm_mmu_page_fault+0xca/0x3c0 arch/x86/kvm/mmu/mmu.c:5059
handle_ept_misconfig+0x96/0x150 arch/x86/kvm/vmx/vmx.c:5375
vmx_handle_exit+0x2fd/0x7e0 arch/x86/kvm/vmx/vmx.c:6068
vcpu_enter_guest+0x199b/0x23b0 arch/x86/kvm/x86.c:9027
vcpu_run+0x24e/0x690 arch/x86/kvm/x86.c:9092
kvm_arch_vcpu_ioctl_run+0x362/0x660 arch/x86/kvm/x86.c:9309
kvm_vcpu_ioctl+0x562/0x8f0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3234
vfs_ioctl fs/ioctl.c:48 [inline]
__do_sys_ioctl fs/ioctl.c:753 [inline]
__se_sys_ioctl+0xcb/0x140 fs/ioctl.c:739
__x64_sys_ioctl+0x3f/0x50 fs/ioctl.c:739
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 22438 Comm: syz-executor.5 Not tainted 5.10.0-rc6-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================


---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status 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.