[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200206171349-mutt-send-email-mst@kernel.org>
Date: Thu, 6 Feb 2020 17:17:19 -0500
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Christian Borntraeger <borntraeger@...ibm.com>
Cc: eperezma@...hat.com,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
kvm list <kvm@...r.kernel.org>,
Halil Pasic <pasic@...ux.ibm.com>
Subject: Re: vhost changes (batched) in linux-next after 12/13 trigger random
crashes in KVM guests after reboot
On Thu, Feb 06, 2020 at 04:12:21PM +0100, Christian Borntraeger wrote:
>
>
> On 06.02.20 15:22, eperezma@...hat.com wrote:
> > Hi Christian.
> >
> > Could you try this patch on top of ("38ced0208491 vhost: use batched version by default")?
> >
> > It will not solve your first random crash but it should help with the lost of network connectivity.
> >
> > Please let me know how does it goes.
>
>
> 38ced0208491 + this seem to be ok.
>
> Not sure if you can make out anything of this (and the previous git bisect log)
Yes it does - that this is just bad split-up of patches, and there's
still a real bug that caused worse crashes :)
So I just pushed batch-v4.
I expect that will fail, and bisect to give us
vhost: batching fetches
Can you try that please?
Powered by blists - more mailing lists