From: syzbot <syzbot+30d8503d558f3d50306b@syzkaller.appspotmail.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
pbonzini@redhat.com, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [kvm?] WARNING in kvm_mmu_notifier_invalidate_range_start (4)
Date: Fri, 10 May 2024 04:08:30 -0700 [thread overview]
Message-ID: <0000000000004574160618178e1e@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 2b84edefcad1 Add linux-next specific files for 20240506
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16f76404980000
kernel config: https://syzkaller.appspot.com/x/.config?x=b499929e4aaba1af
dashboard link: https://syzkaller.appspot.com/bug?extid=30d8503d558f3d50306b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6a22cf95ee14/disk-2b84edef.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f5c45b515282/vmlinux-2b84edef.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9bf98258a662/bzImage-2b84edef.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+30d8503d558f3d50306b@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 16762 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:595 __kvm_handle_hva_range arch/x86/kvm/../../../virt/kvm/kvm_main.c:595 [inline]
WARNING: CPU: 0 PID: 16762 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:595 kvm_mmu_notifier_invalidate_range_start+0xa63/0xc10 arch/x86/kvm/../../../virt/kvm/kvm_main.c:787
Modules linked in:
CPU: 0 PID: 16762 Comm: syz-executor.1 Not tainted 6.9.0-rc7-next-20240506-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:__kvm_handle_hva_range arch/x86/kvm/../../../virt/kvm/kvm_main.c:595 [inline]
RIP: 0010:kvm_mmu_notifier_invalidate_range_start+0xa63/0xc10 arch/x86/kvm/../../../virt/kvm/kvm_main.c:787
Code: c6 05 fb 42 8b 0e 01 48 c7 c7 80 be c1 8b be 03 04 00 00 48 c7 c2 20 9f c1 8b e8 b8 a6 66 00 e9 f6 f8 ff ff e8 8e f5 89 00 90 <0f> 0b 90 e9 28 ff ff ff e8 80 f5 89 00 90 0f 0b 90 e9 c9 f6 ff ff
RSP: 0018:ffffc9000a29e940 EFLAGS: 00010283
RAX: ffffffff810c23a2 RBX: 0000000020000000 RCX: 0000000000040000
RDX: ffffc9001580a000 RSI: 00000000000039aa RDI: 00000000000039ab
RBP: ffffc9000a29eaf0 R08: ffffffff810c1bb6 R09: 0000000000000000
R10: ffffc9000a29ea40 R11: fffff52001453d4d R12: dffffc0000000000
R13: ffffc9000a29ea40 R14: 0000000020000000 R15: 1ffff92001453dc4
FS: 00007f1c65b3f6c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0f815a8000 CR3: 00000000201c0000 CR4: 00000000003526f0
DR0: 000000000000e8ca DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
mn_hlist_invalidate_range_start mm/mmu_notifier.c:476 [inline]
__mmu_notifier_invalidate_range_start+0x45e/0x890 mm/mmu_notifier.c:531
mmu_notifier_invalidate_range_start include/linux/mmu_notifier.h:439 [inline]
try_to_unmap_one+0x9a0/0x3290 mm/rmap.c:1664
rmap_walk_file+0x52f/0x9f0 mm/rmap.c:2669
try_to_unmap+0x219/0x2e0
unmap_folio+0x197/0x370 mm/huge_memory.c:2685
split_huge_page_to_list_to_order+0xbf6/0x1cd0 mm/huge_memory.c:3187
split_folio_to_list_to_order include/linux/huge_mm.h:581 [inline]
split_folio_to_order include/linux/huge_mm.h:586 [inline]
truncate_inode_partial_folio+0x470/0x740 mm/truncate.c:242
shmem_undo_range+0x9a5/0x1df0 mm/shmem.c:1023
shmem_truncate_range mm/shmem.c:1114 [inline]
shmem_fallocate+0x497/0x11f0 mm/shmem.c:3117
vfs_fallocate+0x564/0x6c0 fs/open.c:330
madvise_remove mm/madvise.c:1012 [inline]
madvise_vma_behavior mm/madvise.c:1036 [inline]
madvise_walk_vmas mm/madvise.c:1268 [inline]
do_madvise+0x192a/0x44d0 mm/madvise.c:1464
__do_sys_madvise mm/madvise.c:1481 [inline]
__se_sys_madvise mm/madvise.c:1479 [inline]
__x64_sys_madvise+0xa6/0xc0 mm/madvise.c:1479
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f1c64e7dca9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 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 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f1c65b3f0c8 EFLAGS: 00000246 ORIG_RAX: 000000000000001c
RAX: ffffffffffffffda RBX: 00007f1c64fac050 RCX: 00007f1c64e7dca9
RDX: 0000000000000009 RSI: 000000000060000b RDI: 0000000020000000
RBP: 00007f1c64ec947e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f1c64fac050 R15: 00007ffe73a84cc8
</TASK>
---
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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
reply other threads:[~2024-05-10 11:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000004574160618178e1e@google.com \
--to=syzbot+30d8503d558f3d50306b@syzkaller.appspotmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).