From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Maxim Levitsky <mlevitsk@redhat.com>
Cc: syzbot <syzbot+a8ad3ee1525a0c4b40ec@syzkaller.appspotmail.com>,
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,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
vkuznets@redhat.com, wanpengli@tencent.com, x86@kernel.org
Subject: Re: [syzbot] WARNING in kvm_mmu_uninit_tdp_mmu (2)
Date: Thu, 28 Apr 2022 19:22:43 +0200 [thread overview]
Message-ID: <d1e4eaba-2dcd-ec08-4e23-98ab8ea6c37b@redhat.com> (raw)
In-Reply-To: <YmqzoFqdmH1WuPv0@google.com>
On 4/28/22 17:32, Sean Christopherson wrote:
> On Tue, Apr 26, 2022, Maxim Levitsky wrote:
>> I can reproduce this in a VM, by running and CTRL+C'in my ipi_stress test,
>
> Can you post your ipi_stress test? I'm curious to see if I can repro, and also
> very curious as to what might be unique about your test. I haven't been able to
> repro the syzbot test, nor have I been able to repro by killing VMs/tests.
Did you test with CONFIG_PREEMPT=y?
(BTW, the fact that it reproduces under 5.17 is a mixed blessing,
because it means that we can analyze/stare at a simpler codebase).
Paolo
next prev parent reply other threads:[~2022-04-28 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 10:56 [syzbot] WARNING in kvm_mmu_uninit_tdp_mmu (2) syzbot
2022-04-26 16:20 ` Maxim Levitsky
2022-04-28 7:25 ` Maxim Levitsky
2022-04-28 15:32 ` Sean Christopherson
2022-04-28 17:16 ` Maxim Levitsky
2022-04-28 17:21 ` Maxim Levitsky
2022-04-28 17:22 ` Paolo Bonzini [this message]
2022-04-28 17:26 ` Maxim Levitsky
2022-04-28 17:43 ` Sean Christopherson
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=d1e4eaba-2dcd-ec08-4e23-98ab8ea6c37b@redhat.com \
--to=pbonzini@redhat.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=mlevitsk@redhat.com \
--cc=seanjc@google.com \
--cc=syzbot+a8ad3ee1525a0c4b40ec@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox