From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: qemu-devel@nongnu.org, josh.durgin@inktank.com,
ceph-devel@vger.kernel.org, pbonzini@redhat.com
Subject: Re: [PATCH] rbd block driver fix race between aio completition and aio cancel
Date: Thu, 29 Nov 2012 14:58:51 +0100 [thread overview]
Message-ID: <20121129135851.GA13694@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1353578419-5481-1-git-send-email-s.priebe@profihost.ag>
On Thu, Nov 22, 2012 at 11:00:19AM +0100, Stefan Priebe wrote:
> @@ -406,10 +401,11 @@ static void qemu_rbd_complete_aio(RADOSCB *rcb)
> acb->ret = r;
> }
> }
> + acb->status = 0;
> +
I suggest doing this in the BH. The qemu_aio_wait() loop in
qemu_rbd_aio_cancel() needs to wait until the BH has executed. By
clearing status in the BH we ensure that no matter in which order
qemu_aio_wait() invokes BHs and callbacks, we'll always wait until the
BH has completed before ending the while loop in qemu_rbd_aio_cancel().
> @@ -737,7 +741,8 @@ static BlockDriverAIOCB *rbd_start_aio(BlockDriverState *bs,
> failed:
> g_free(rcb);
> s->qemu_aio_count--;
> - qemu_aio_release(acb);
> + if (!acb->cancelled)
> + qemu_aio_release(acb);
> return NULL;
> }
This scenario is impossible. We haven't returned the acb back to the
caller yet so they could not have invoked qemu_aio_cancel().
Stefan
next prev parent reply other threads:[~2012-11-29 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 10:00 [PATCH] rbd block driver fix race between aio completition and aio cancel Stefan Priebe
2012-11-24 19:54 ` [Qemu-devel] " Blue Swirl
2012-11-24 20:21 ` Stefan Priebe
2012-11-27 22:42 ` Josh Durgin
2012-11-29 15:24 ` Paolo Bonzini
2012-11-29 13:58 ` Stefan Hajnoczi [this message]
2012-11-29 14:32 ` Stefan Priebe - Profihost AG
-- strict thread matches above, loose matches on Subject: below --
2012-11-19 20:39 (no subject) Stefan Priebe
2012-11-19 20:43 ` [PATCH] rbd block driver fix race between aio completition and aio cancel Stefan Priebe
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=20121129135851.GA13694@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=josh.durgin@inktank.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=s.priebe@profihost.ag \
/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.