From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sean Christopherson <sean.j.christopherson@intel.com>
Subject: Re: 5.0-rc1 KVM inspired "BUG: Bad page state in process" spew
Date: Mon, 14 Jan 2019 07:46:20 -0800
Message-ID: <20190114154619.GA5141@linux.intel.com>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Adam Borowski <kilobyte@angband.pl>, kvm <kvm@vger.kernel.org>,
        lkml <linux-kernel@vger.kernel.org>
To: Mike Galbraith <efault@gmx.de>
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <1547275382.26908.7.camel@gmx.de>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

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").

Nested VMs are great for bisecting KVM issues :)