Hello,
syzbot found the following issue on:
HEAD commit: 32f741b0 Merge tag 'powerpc-5.10-5' of git://git.kernel.or..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=160f0bf7500000
kernel config:
https://syzkaller.appspot.com/x/.config?x=c949fed53798f819
dashboard link:
https://syzkaller.appspot.com/bug?extid=7a5a25f380e667b89a9b
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+7a5a25...@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in kvm_mmu_notifier_invalidate_range_end / kvm_mmu_notifier_invalidate_range_start
read-write to 0xffffc900042c71b8 of 8 bytes by task 6636 on cpu 0:
kvm_mmu_notifier_invalidate_range_start+0x58/0x1c0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:482
mn_hlist_invalidate_range_start mm/mmu_notifier.c:493 [inline]
__mmu_notifier_invalidate_range_start+0x22a/0x380 mm/mmu_notifier.c:525
mmu_notifier_invalidate_range_start include/linux/mmu_notifier.h:453 [inline]
wp_page_copy+0x38a/0x1490 mm/memory.c:2864
do_wp_page+0x482/0x6c0 arch/x86/include/asm/atomic.h:95
handle_pte_fault mm/memory.c:4392 [inline]
__handle_mm_fault mm/memory.c:4509 [inline]
handle_mm_fault+0x13d1/0x1770 mm/memory.c:4607
faultin_page mm/gup.c:885 [inline]
__get_user_pages+0x8ec/0xe50 mm/gup.c:1097
__get_user_pages_locked mm/gup.c:1283 [inline]
get_user_pages_unlocked+0x133/0x550 mm/gup.c:2023
hva_to_pfn_slow+0x74/0x270 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1857
hva_to_pfn arch/x86/kvm/../../../virt/kvm/kvm_main.c:1965 [inline]
__gfn_to_pfn_memslot+0x2aa/0x640 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2021
try_async_pf+0xab/0x450 arch/x86/kvm/mmu/mmu.c:3660
direct_page_fault+0x1f3/0x770 arch/x86/kvm/mmu/mmu.c:3705
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_violation+0x277/0x350 arch/x86/kvm/vmx/vmx.c:5357
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
read to 0xffffc900042c71b8 of 8 bytes by task 6635 on cpu 1:
kvm_mmu_notifier_invalidate_range_end+0x59/0x90 arch/x86/kvm/../../../virt/kvm/kvm_main.c:517
mn_hlist_invalidate_end mm/mmu_notifier.c:560 [inline]
__mmu_notifier_invalidate_range_end+0x18e/0x210 mm/mmu_notifier.c:580
mmu_notifier_invalidate_range_only_end include/linux/mmu_notifier.h:486 [inline]
wp_page_copy+0x929/0x1490 mm/memory.c:2941
do_wp_page+0x482/0x6c0 arch/x86/include/asm/atomic.h:95
handle_pte_fault mm/memory.c:4392 [inline]
__handle_mm_fault mm/memory.c:4509 [inline]
handle_mm_fault+0x13d1/0x1770 mm/memory.c:4607
do_user_addr_fault+0x33e/0x730 arch/x86/mm/fault.c:1372
handle_page_fault arch/x86/mm/fault.c:1429 [inline]
exc_page_fault+0x91/0x290 arch/x86/mm/fault.c:1485
asm_exc_page_fault+0x1e/0x30 arch/x86/include/asm/idtentry.h:583
Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 6635 Comm: syz-executor.3 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.