From: syzbot <syzbot+717ed82268812a643b28@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
jmattson@google.com, joro@8bytes.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
pbonzini@redhat.com, seanjc@google.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
vkuznets@redhat.com, wanpengli@tencent.com, x86@kernel.org
Subject: [syzbot] general protection fault in kvm_mmu_uninit_tdp_mmu
Date: Fri, 25 Mar 2022 06:10:26 -0700 [thread overview]
Message-ID: <000000000000a5cb1305db0aaf48@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: f9006d9269ea Add linux-next specific files for 20220321
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=101191bd700000
kernel config: https://syzkaller.appspot.com/x/.config?x=c1619ffa2b0259a1
dashboard link: https://syzkaller.appspot.com/bug?extid=717ed82268812a643b28
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=109e8f5d700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1666180b700000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+717ed82268812a643b28@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xdffffc0000000038: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x00000000000001c0-0x00000000000001c7]
CPU: 0 PID: 3614 Comm: syz-executor358 Tainted: G W 5.17.0-next-20220321-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:flush_workqueue+0xf8/0x1440 kernel/workqueue.c:2828
Code: ff 89 de e8 ea 02 2c 00 84 db 0f 84 28 0f 00 00 e8 fd fe 2b 00 48 8b 85 e8 fe ff ff 48 8d b8 c0 01 00 00 48 89 f8 48 c1 e8 03 <42> 0f b6 04 20 84 c0 74 08 3c 03 0f 8e f9 12 00 00 48 8b 85 e8 fe
RSP: 0018:ffffc90003affba8 EFLAGS: 00010202
RAX: 0000000000000038 RBX: 0000000000000001 RCX: 0000000000000000
RDX: ffff8880184b57c0 RSI: ffffffff814caa33 RDI: 00000000000001c0
RBP: ffffc90003affd18 R08: 0000000000000002 R09: 0000000000000001
R10: ffffffff814caa26 R11: 0000000000000000 R12: dffffc0000000000
R13: ffffc90003affd70 R14: ffffc90003b29000 R15: ffffc90003b2a240
FS: 00007f26eaecd700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020404030 CR3: 00000000246a9000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
kvm_mmu_uninit_tdp_mmu+0x7f/0x170 arch/x86/kvm/mmu/tdp_mmu.c:51
kvm_arch_destroy_vm+0x350/0x470 arch/x86/kvm/x86.c:11799
kvm_create_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:1144 [inline]
kvm_dev_ioctl_create_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:4736 [inline]
kvm_dev_ioctl+0x104d/0x1c00 arch/x86/kvm/../../../virt/kvm/kvm_main.c:4791
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl fs/ioctl.c:856 [inline]
__x64_sys_ioctl+0x193/0x200 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0x80 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f26eaf5dac9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 11 15 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f26eaecd308 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f26eafe5448 RCX: 00007f26eaf5dac9
RDX: 0000000000000000 RSI: 000000000000ae01 RDI: 0000000000000005
RBP: 00007f26eafe5440 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f26eafe544c
R13: 00007f26eafb3074 R14: 6d766b2f7665642f R15: 0000000000022000
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:flush_workqueue+0xf8/0x1440 kernel/workqueue.c:2828
Code: ff 89 de e8 ea 02 2c 00 84 db 0f 84 28 0f 00 00 e8 fd fe 2b 00 48 8b 85 e8 fe ff ff 48 8d b8 c0 01 00 00 48 89 f8 48 c1 e8 03 <42> 0f b6 04 20 84 c0 74 08 3c 03 0f 8e f9 12 00 00 48 8b 85 e8 fe
RSP: 0018:ffffc90003affba8 EFLAGS: 00010202
RAX: 0000000000000038 RBX: 0000000000000001 RCX: 0000000000000000
RDX: ffff8880184b57c0 RSI: ffffffff814caa33 RDI: 00000000000001c0
RBP: ffffc90003affd18 R08: 0000000000000002 R09: 0000000000000001
R10: ffffffff814caa26 R11: 0000000000000000 R12: dffffc0000000000
R13: ffffc90003affd70 R14: ffffc90003b29000 R15: ffffc90003b2a240
FS: 00007f26eaecd700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020404030 CR3: 00000000246a9000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: ff 89 de e8 ea 02 decl 0x2eae8de(%rcx)
6: 2c 00 sub $0x0,%al
8: 84 db test %bl,%bl
a: 0f 84 28 0f 00 00 je 0xf38
10: e8 fd fe 2b 00 callq 0x2bff12
15: 48 8b 85 e8 fe ff ff mov -0x118(%rbp),%rax
1c: 48 8d b8 c0 01 00 00 lea 0x1c0(%rax),%rdi
23: 48 89 f8 mov %rdi,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 0f b6 04 20 movzbl (%rax,%r12,1),%eax <-- trapping instruction
2f: 84 c0 test %al,%al
31: 74 08 je 0x3b
33: 3c 03 cmp $0x3,%al
35: 0f 8e f9 12 00 00 jle 0x1334
3b: 48 rex.W
3c: 8b .byte 0x8b
3d: 85 e8 test %ebp,%eax
3f: fe .byte 0xfe
---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2022-03-25 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 13:10 syzbot [this message]
2022-03-25 15:51 ` [syzbot] general protection fault in kvm_mmu_uninit_tdp_mmu Pavel Skripkin
2022-03-25 16:19 ` syzbot
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=000000000000a5cb1305db0aaf48@google.com \
--to=syzbot+717ed82268812a643b28@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.