From: Kevin Wolf <kwolf@redhat.com>
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>
Subject: Re: [Qemu-devel] [Qemu-block] [Bug 1570134] Re: While committing snapshot qemu crashes with SIGABRT
Date: Thu, 21 Apr 2016 13:43:59 +0200 [thread overview]
Message-ID: <20160421114359.GE4193@noname.redhat.com> (raw)
In-Reply-To: <CAFEAcA8d4QujkAQM9O-m_v=N03NXmV-yT57QcvpwdMtT0Dqktw@mail.gmail.com>
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
next prev parent reply other threads:[~2016-04-21 11:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 23:18 [Qemu-devel] [Bug 1570134] [NEW] While committing snapshot qemu crashes with SIGABRT Matthew Schumacher
2016-04-14 2:16 ` Fam Zheng
2016-04-14 16:24 ` [Qemu-devel] [Bug 1570134] " Matthew Schumacher
2016-04-14 20:51 ` Matthew Schumacher
2016-04-15 16:30 ` Matthew Schumacher
2016-04-16 21:46 ` Max Reitz
2016-04-16 21:48 ` Max Reitz
2016-04-18 18:59 ` Matthew Schumacher
2016-04-19 22:01 ` Max Reitz
2016-04-20 0:03 ` Matthew Schumacher
2016-04-20 18:09 ` Max Reitz
2016-04-20 20:03 ` Max Reitz
2016-04-21 0:34 ` Fam Zheng
2016-04-21 2:07 ` Fam Zheng
2016-04-21 11:35 ` Peter Maydell
2016-04-21 11:43 ` Kevin Wolf [this message]
2016-04-22 18:55 ` Matthew Schumacher
2016-04-25 1:02 ` Fam Zheng
2016-04-26 5:18 ` Fam Zheng
2016-06-21 16:33 ` T. Huth
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=20160421114359.GE4193@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=1570134@bugs.launchpad.net \
--cc=famz@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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.