linux-kernel - Re: [syzbot] WARNING in kvm_mmu_uninit_tdp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <YmrSNB83b5sKLocw@google.com>
Date:   Thu, 28 Apr 2022 17:43:16 +0000
From:   Sean Christopherson <seanjc@...gle.com>
To:     Maxim Levitsky <mlevitsk@...hat.com>
Cc:     Paolo Bonzini <pbonzini@...hat.com>,
        syzbot <syzbot+a8ad3ee1525a0c4b40ec@...kaller.appspotmail.com>,
        bp@...en8.de, dave.hansen@...ux.intel.com, hpa@...or.com,
        jmattson@...gle.com, joro@...tes.org, kvm@...r.kernel.org,
        linux-kernel@...r.kernel.org, mingo@...hat.com,
        syzkaller-bugs@...glegroups.com, tglx@...utronix.de,
        vkuznets@...hat.com, wanpengli@...cent.com, x86@...nel.org
Subject: Re: [syzbot] WARNING in kvm_mmu_uninit_tdp_mmu (2)

On Thu, Apr 28, 2022, Maxim Levitsky wrote:
> On Thu, 2022-04-28 at 19:22 +0200, Paolo Bonzini wrote:
> > 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?
> 
> yes, I test with CONFIG_PREEMPT but I only enabled it a day ago,
> I think I had seen this warning before, but could bit, I'll check
> if that fails without CONFIG_PREEMPT as well.

I have not tested with CONFIG_PREEMPT.  For some unknown reason the syzbot configs
don't play nice with my VM setup and so I never use them verbatim.  I didn't think
to pull over CONFIG_PREEMPTY.  I'll give that a shot.