From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Mike Galbraith <efault@gmx.de>
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 07:46:20 -0800 [thread overview]
Message-ID: <20190114154619.GA5141@linux.intel.com> (raw)
In-Reply-To: <1547275382.26908.7.camel@gmx.de>
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 :)
next prev parent reply other threads:[~2019-01-14 15:46 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 [this message]
2019-01-14 17:42 ` Mike Galbraith
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=20190114154619.GA5141@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=efault@gmx.de \
--cc=kilobyte@angband.pl \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.