[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+G9fYsC91dc5qp3Fb4nnZ=GzWu_9TG-_RVD2ie6xLmYD77n8w@mail.gmail.com>
Date: Fri, 29 May 2020 01:21:05 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: Sean Christopherson <sean.j.christopherson@...el.com>
Cc: Paolo Bonzini <pbonzini@...hat.com>,
kvm list <kvm@...r.kernel.org>, eesposit@...hat.com,
lkft-triage@...ts.linaro.org,
open list <linux-kernel@...r.kernel.org>,
Shuah Khan <shuah@...nel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>,
Anders Roxell <anders.roxell@...aro.org>,
Andy Lutomirski <luto@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Vivek Goyal <vgoyal@...hat.com>, Gavin Shan <gshan@...hat.com>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: BUG: arch/x86/kvm/mmu/mmu.c:3722: kvm_mmu_load+0x407/0x420
On Fri, 29 May 2020 at 01:08, Sean Christopherson
<sean.j.christopherson@...el.com> wrote:
>
> On Fri, May 29, 2020 at 12:59:40AM +0530, Naresh Kamboju wrote:
> > While running selftest kvm set_memory_region_test on x86_64 linux-next kernel
> > 5.7.0-rc6-next-20200518 the kernel BUG noticed.
> >
> > steps to reproduce: (always reproducible )
> > -------------------------
> > cd /opt/kselftests/default-in-kernel/kvm
> > ./set_memory_region_test
> >
> > BAD: next-20200518 (still reproducible on next-20200526)
> > GOOD: next-20200515
> > git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > kernel config:
> > http://snapshots.linaro.org/openembedded/lkft/lkft/sumo/intel-corei7-64/lkft/linux-next/777/config
> >
> > kernel crash log,
> > -----------------------
> > [ 33.074161] ------------[ cut here ]------------
> > [ 33.079845] kernel BUG at /usr/src/kernel/arch/x86/kvm/mmu/mmu.c:3722!
>
> I'm 99% certain this is already fixed[*], I'll double check to confirm.
Thanks for looking into this problem.
> [*] https://lkml.kernel.org/r/20200527085400.23759-1-sean.j.christopherson@intel.com
I see you made a recent fix (on Wed, 27 May 2020).
Let this patch get into the linux-next tree master and our build system
will pull it and test it. I will report back once it is fixed.
- Naresh
Powered by blists - more mailing lists