[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0a85df4b-ca0a-7e70-51dc-90bd1c460c85@redhat.com>
Date: Fri, 25 Aug 2017 15:40:50 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Adam Borowski <kilobyte@...band.pl>,
Wanpeng Li <kernellwp@...il.com>
Cc: Radim Krčmář <rkrcmar@...hat.com>,
kvm <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: kvm splat in mmu_spte_clear_track_bits
On 25/08/2017 15:14, Adam Borowski wrote:
>>> I would also try commit 1372324b328cd5dabaef5e345e37ad48c63df2a9 to
>>> identify whether it was caused by a KVM change in 4.13 or something
>>> else.
> I've ran different guests for a couple of hours, no explosions. Thus it
> looks like updating Cornelia's email address isn't the cause.
>
> Too bad, there's 15k commits between 1372324b and 7f680d7ec315.
So:
- 4.12 works
- 1372324b328cd5dabaef5e345e37ad48c63df2a9 works
- 4.13-rc6 fails
The next ones to test are going to be
c136b84393d4e340e1b53fc7f737dd5827b19ee5 and 4.13-rc1.
This can be a starting point for bisection or pointing the finger at
someone else.
Powered by blists - more mailing lists