From: Kevin Wolf <kwolf@redhat.com>
To: Chunqiang Tang <ctang@us.ibm.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: QCOW2 bugs releated to qcow2_aio_cancel()
Date: Thu, 03 Feb 2011 18:44:28 +0100 [thread overview]
Message-ID: <4D4AE97C.60307@redhat.com> (raw)
In-Reply-To: <OFE9BAD126.A83D3339-ON8525782C.005D13B8-8525782C.005F351D@us.ibm.com>
Am 03.02.2011 18:21, schrieb Chunqiang Tang:
> Hi Kevin,
>
> Fast Virtual Disk (FVD) has an automated testing tool (see
> http://wiki.qemu.org/Features/FVD/Engineering). For a long time, I knew
> that QCOW2 could not pass the automated tests. Today I finally sit down to
> look into those bugs. I already submitted multiple patches for different
> bugs, but there is one case that I am not certain how to handle. Instead
> of creating a potentially broken patch, I though you might be able to
> handle it better than me. Bugs showed up when the testing tool injected
> aio cancel.
We have discussed this before and yes, aio_cancel is a problem. It is
very hard to do this correctly, and so most block drivers just wait for
completion instead of actually cancelling anything.
Given that a cancel shouldn't happen too often, I think it would be
reasonable to take the same approach for qcow2. I don't think adding a
lot of complexity for getting this right is justified.
Stefan, what do you think? Maybe we could even have a default
implementation in generic block code?
Kevin
next prev parent reply other threads:[~2011-02-03 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 17:21 [Qemu-devel] QCOW2 bugs releated to qcow2_aio_cancel() Chunqiang Tang
2011-02-03 17:44 ` Kevin Wolf [this message]
2011-02-04 5:58 ` [Qemu-devel] " 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=4D4AE97C.60307@redhat.com \
--to=kwolf@redhat.com \
--cc=ctang@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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.