From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] block: fix streaming/closing race
Date: Fri, 30 Mar 2012 10:31:13 +0200 [thread overview]
Message-ID: <4F756F51.5010603@redhat.com> (raw)
In-Reply-To: <20120330071921.GB16159@stefanha-thinkpad.localdomain>
Il 30/03/2012 09:19, Stefan Hajnoczi ha scritto:
>> > +void block_job_cancel_sync(BlockJob *job)
>> > +{
>> > + BlockDriverState *bs = job->bs;
>> > +
>> > + assert(bs->job == job);
>> > + block_job_cancel(job);
>> > + while (bs->job != NULL && bs->job->busy) {
> It's not clear to me why we have a busy flag.
Because the coroutine does not restart if you do qemu_aio_wait and the
coroutine is waiting in co_sleep. So the busy flag communicates that
the coroutine is quiescent and, when cancelled, will not issue any new I/O.
However, even this is not enough. It fixes a race with closing, but not
with deleting bs. So the bug does not show anymore when you quit QEMU
(because the coroutine is not restarted), but it is still there if you
hot-unplug a device while streaming is in effect.
> Is canceling and waiting for bs->job == NULL not enough? Perhaps
> you're trying to take a shortcut and not wait until the job is fully
> stopped
No, simply it's impossible to wait for full completion with qemu_aio_wait.
Paolo
next prev parent reply other threads:[~2012-03-30 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 16:08 [Qemu-devel] [PATCH] block: fix streaming/closing race Paolo Bonzini
2012-03-30 7:19 ` Stefan Hajnoczi
2012-03-30 8:31 ` Paolo Bonzini [this message]
2012-03-30 10:00 ` Paolo Bonzini
2012-03-30 10:25 ` Stefan Hajnoczi
2012-03-30 10:29 ` Paolo Bonzini
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=4F756F51.5010603@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.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).