From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Galbraith Subject: Re: 5.0-rc1 KVM inspired "BUG: Bad page state in process" spew Date: Mon, 14 Jan 2019 18:42:16 +0100 Message-ID: <1547487736.31585.21.camel@gmx.de> References: <1547012338.4926.11.camel@gmx.de> <20190109144257.erwh52326ucgc5tw@angband.pl> <1547046196.31155.1.camel@gmx.de> <20190109192637.GA1697@linux.intel.com> <1547275382.26908.7.camel@gmx.de> <20190114154619.GA5141@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: 7bit Cc: Adam Borowski , kvm , lkml To: Sean Christopherson Return-path: In-Reply-To: <20190114154619.GA5141@linux.intel.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Mon, 2019-01-14 at 07:46 -0800, Sean Christopherson wrote: > On Sat, Jan 12, 2019 at 07:43:02AM +0100, Mike Galbraith wrote: > > On Wed, 2019-01-09 at 11:26 -0800, Sean Christopherson wrote: > > > > > > I'll try to bisect. > > > > Good luck with that. I gave it a go, but that apparently invalidated > > the warrantee of my vm image :) > > This is fixed in v5.0-rc2 by commit ba422731316d ("mm/mmu_notifier: > mm/rmap.c: Fix a mmu_notifier range bug in try_to_unmap_one"). Good to hear. > Nested VMs are great for bisecting KVM issues :) I tried nesting dolls (to speed bisection.. hah!), but couldn't reliable trigger the problem with my reproducer. Even if it had, nested VMs are pretty cool, but not the _least bit_ fast :) -Mike