From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48086)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1atD1j-0004VF-Ob
	for qemu-devel@nongnu.org; Thu, 21 Apr 2016 07:44:08 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1atD1i-0002yW-Sq
	for qemu-devel@nongnu.org; Thu, 21 Apr 2016 07:44:07 -0400
Date: Thu, 21 Apr 2016 13:43:59 +0200
From: Kevin Wolf <kwolf@redhat.com>
Message-ID: <20160421114359.GE4193@noname.redhat.com>
References: <20160413231801.31850.67186.malonedeb@chaenomeles.canonical.com>
	<20160420000318.17358.96092.malone@soybean.canonical.com>
	<5717C5F3.90603@redhat.com>
	<CAFEAcA8d4QujkAQM9O-m_v=N03NXmV-yT57QcvpwdMtT0Dqktw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAFEAcA8d4QujkAQM9O-m_v=N03NXmV-yT57QcvpwdMtT0Dqktw@mail.gmail.com>
Subject: Re: [Qemu-devel] [Qemu-block] [Bug 1570134] Re: While committing
 snapshot qemu crashes with SIGABRT
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Max Reitz <mreitz@redhat.com>, Fam Zheng <famz@redhat.com>, Qemu-block <qemu-block@nongnu.org>, QEMU Developers <qemu-devel@nongnu.org>, Stefan Hajnoczi <stefanha@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>, Bug 1570134 <1570134@bugs.launchpad.net>

Am 21.04.2016 um 13:35 hat Peter Maydell geschrieben:
> On 20 April 2016 at 19:09, Max Reitz <mreitz@redhat.com> wrote:
> > On 20.04.2016 02:03, Matthew Schumacher wrote:
> >> Qemu still crashes for me, but the debug is again very different.  When
> >> I attach to the qemu process from gdb, it is unable to provide a
> >> backtrace when it crashes.  The log file is different too.  Any ideas?
> >>
> >> qemu-system-x86_64: block.c:2307: bdrv_replace_in_backing_chain:
> >> Assertion `!bdrv_requests_pending(old)' failed.
> >
> > This message is exactly the same as you saw in 2.5.1, so I guess we've
> > at least averted a regression in 2.6.0.
> 
> Could somebody summarize for me the state of this bug w.r.t. the
> upcoming release? In particular:
>  * are there any patches on-list for it which should go into rc3?
>  * are there any further problems which we plan to fix for 2.6 but
>    which there aren't patches for yet?

The first part of the bug (the regression since 2.5) was fixed with the
pull request that I sent you yesterday. For the remaining part, Fam sent
this patch, which hasn't been applied yet:

[PATCH for-2.6] virtio: Register host notifier handler as external

Kevin