From: Fam Zheng <famz@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
pbonzini@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/1] block: Workaround for the iotests errors
Date: Fri, 24 Nov 2017 16:41:20 +0800 [thread overview]
Message-ID: <20171124084120.GC3108@lemon> (raw)
In-Reply-To: <20171124061234.GB14612@localhost.localdomain>
On Fri, 11/24 01:12, Jeff Cody wrote:
> On Fri, Nov 24, 2017 at 01:57:46AM +0800, Fam Zheng wrote:
> > Jeff's block job patch made the latent drain bug visible, and I find this
> > patch, which by itself also makes some sense, can hide it again. :) With it
> > applied we are at least back to the ground where patchew's iotests (make
> > docker-test-block@fedora) can pass.
> >
>
> Unfortunately, I am still seeing segfaults and aborts even with this patch.
> For instance, on tests: 097 141 176.
OK, so the graph change during bdrv_parent_drained_begin/end still bits. We'll
need more code to secure it.
Fam
next prev parent reply other threads:[~2017-11-24 8:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 17:57 [Qemu-devel] [PATCH 0/1] block: Workaround for the iotests errors Fam Zheng
2017-11-23 17:57 ` [Qemu-devel] [PATCH 1/1] block: Don't poll for drain end Fam Zheng
2017-11-24 6:12 ` [Qemu-devel] [PATCH 0/1] block: Workaround for the iotests errors Jeff Cody
2017-11-24 8:41 ` Fam Zheng [this message]
2017-11-24 16:39 ` Kevin Wolf
2017-11-28 2:53 ` Fam Zheng
2017-11-27 23:29 ` Kevin Wolf
2017-11-28 0:21 ` [Qemu-devel] [Qemu-block] " John Snow
2017-11-28 5:43 ` [Qemu-devel] " Jeff Cody
2017-11-28 11:42 ` Kevin Wolf
2017-11-28 12:28 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
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=20171124084120.GC3108@lemon \
--to=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--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 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).