From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: John Snow <jsnow@redhat.com>,
Quytelda Kahja <quytelda@tamalin.org>,
qemu-devel@nongnu.org, Qemu-block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-block] [BUG] qed_aio_write_alloc: Assertion `s->allocating_acb == NULL' failed.
Date: Fri, 29 Jun 2018 22:35:28 +0200 [thread overview]
Message-ID: <20180629203528.GM15588@localhost.localdomain> (raw)
In-Reply-To: <007fb94d-5a04-0ee1-5d1b-6fd41e67c9a4@redhat.com>
Am 29.06.2018 um 22:16 hat Eric Blake geschrieben:
> On 06/29/2018 03:07 PM, John Snow wrote:
> > CC Qemu Block; looks like QED is a bit busted.
> >
> > On 06/27/2018 10:25 AM, Quytelda Kahja wrote:
> > > Hello all,
> > > I wanted to submit a bug report in the tracker, but it seem to require
> > > an Ubuntu One account, which I'm having trouble with, so I'll just
> > > give it here and hopefully somebody can make use of it. The issue
> > > seems to be in an experimental format, so it's likely not very
> > > consequential anyway.
>
> Analysis in another thread may be relevant:
>
> https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg08963.html
The assertion there was:
qemu-system-x86_64: block.c:3434: bdrv_replace_node: Assertion `!atomic_read(&to->in_flight)' failed.
Which quite clearly pointed to a drain bug. This one, however, doesn't
seem to be related to drain, so I think it's probably a different bug.
Kevin
next prev parent reply other threads:[~2018-06-29 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 14:25 [Qemu-devel] [BUG] qed_aio_write_alloc: Assertion `s->allocating_acb == NULL' failed Quytelda Kahja
2018-06-29 20:07 ` John Snow
2018-06-29 20:16 ` Eric Blake
2018-06-29 20:35 ` Kevin Wolf [this message]
2018-07-02 13:55 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
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=20180629203528.GM15588@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quytelda@tamalin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).