From: Mike Galbraith <efault@gmx.de>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Adam Borowski <kilobyte@angband.pl>, kvm <kvm@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: 5.0-rc1 KVM inspired "BUG: Bad page state in process" spew
Date: Mon, 14 Jan 2019 18:42:16 +0100 [thread overview]
Message-ID: <1547487736.31585.21.camel@gmx.de> (raw)
In-Reply-To: <20190114154619.GA5141@linux.intel.com>
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
prev parent reply other threads:[~2019-01-14 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 5:38 5.0-rc1 KVM inspired "BUG: Bad page state in process" spew Mike Galbraith
2019-01-09 14:42 ` Adam Borowski
2019-01-09 15:03 ` Mike Galbraith
2019-01-09 19:26 ` Sean Christopherson
2019-01-12 6:43 ` Mike Galbraith
2019-01-14 15:46 ` Sean Christopherson
2019-01-14 17:42 ` Mike Galbraith [this message]
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=1547487736.31585.21.camel@gmx.de \
--to=efault@gmx.de \
--cc=kilobyte@angband.pl \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
/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