From: Sean Christopherson <seanjc@google.com>
To: "Sabri N. Ferreiro" <snferreiro1@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
sunhao.th@gmail.com
Subject: Re: WARNING in kvm_mmu_uninit_tdp_mmu
Date: Tue, 11 Jan 2022 19:37:50 +0000 [thread overview]
Message-ID: <Yd3cjllVD4vS17kG@google.com> (raw)
In-Reply-To: <CAKG+3NTTHD3iXgK67B4R3e+ScZ+vW5H4FdwLYy9CR5oBF44DOA@mail.gmail.com>
On Sun, Jan 09, 2022, Sabri N. Ferreiro wrote:
> Hi,
>
> When using Syzkaller to fuzz the Linux kernel, it triggers the following crash.
>
> HEAD commit: a7904a538933 Linux 5.16-rc6
> git tree: upstream
> console output: https://pastebin.com/raw/keWCUeJ2
> kernel config: https://docs.google.com/document/d/1w94kqQ4ZSIE6BW-5WIhqp4_Zh7XTPH57L5OF2Xb6O6o/view
> C reproducer: https://pastebin.com/raw/kSxa6Yit
> Syzlang reproducer: https://pastebin.com/raw/2RMu8p6E
>
> If you fix this issue, please add the following tag to the commit:
> Reported-by: Yuheng Shen mosesfonscqf75@gmail.com
>
> ------------[ cut here ]------------
> WARNING: CPU: 5 PID: 29657 at arch/x86/kvm/mmu/tdp_mmu.c:46
> kvm_mmu_uninit_tdp_mmu+0xb9/0xf0
I wasn't able to reproduce to confirm, but this is more than likely fixed by
commit 3a0f64de479c ("KVM: x86/mmu: Don't advance iterator after restart due to yielding"),
which didn't land until 5.16-rc7.
prev parent reply other threads:[~2022-01-11 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 14:05 Sabri N. Ferreiro
2022-01-11 19:37 ` Sean Christopherson [this message]
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=Yd3cjllVD4vS17kG@google.com \
--to=seanjc@google.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=snferreiro1@gmail.com \
--cc=sunhao.th@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome