From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fix raw_aio_read\write error handling
Date: Thu, 29 Jan 2009 11:02:55 -0600 [thread overview]
Message-ID: <4981E13F.5010700@us.ibm.com> (raw)
In-Reply-To: <4981BFD0.8020006@eu.citrix.com>
Stefano Stabellini wrote:
> Currently when qemu_paio_read or qemu_paio_write return an error we call
> qemu_aio_release without removing the request from the list.
> I know that in the current implementation qemu_paio_write\read don't return
> any error, but still the behavior is wrong, especially considering
> that the implementation of these two functions is likely to change in is
> the future.
> This patch fixes the problem adding a raw_aio_remove function that
> removes the callback from the queue and also calls qemu_aio_release.
> raw_aio_remove is called by raw_aio_read, raw_aio_write and
> raw_aio_cancel.
>
Good catch. Applied. Thanks.
Regards,
Anthony Liguori
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
>
> ---
>
> diff --git a/block-raw-posix.c b/block-raw-posix.c
> index 4404eb1..ac88fc3 100644
> --- a/block-raw-posix.c
> +++ b/block-raw-posix.c
> @@ -598,6 +598,24 @@ static void raw_aio_em_cb(void* opaque)
> qemu_aio_release(acb);
> }
>
> +static void raw_aio_remove(RawAIOCB *acb)
> +{
> + RawAIOCB **pacb;
> +
> + /* remove the callback from the queue */
> + pacb = &posix_aio_state->first_aio;
> + for(;;) {
> + if (*pacb == NULL) {
> + break;
> + } else if (*pacb == acb) {
> + *pacb = acb->next;
> + qemu_aio_release(acb);
> + break;
> + }
> + pacb = &acb->next;
> + }
> +}
> +
> static BlockDriverAIOCB *raw_aio_read(BlockDriverState *bs,
> int64_t sector_num, uint8_t *buf, int nb_sectors,
> BlockDriverCompletionFunc *cb, void *opaque)
> @@ -623,7 +641,7 @@ static BlockDriverAIOCB *raw_aio_read(BlockDriverState *bs,
> if (!acb)
> return NULL;
> if (qemu_paio_read(&acb->aiocb) < 0) {
> - qemu_aio_release(acb);
> + raw_aio_remove(acb);
> return NULL;
> }
> return &acb->common;
> @@ -654,7 +672,7 @@ static BlockDriverAIOCB *raw_aio_write(BlockDriverState *bs,
> if (!acb)
> return NULL;
> if (qemu_paio_write(&acb->aiocb) < 0) {
> - qemu_aio_release(acb);
> + raw_aio_remove(acb);
> return NULL;
> }
> return &acb->common;
> @@ -664,7 +682,6 @@ static void raw_aio_cancel(BlockDriverAIOCB *blockacb)
> {
> int ret;
> RawAIOCB *acb = (RawAIOCB *)blockacb;
> - RawAIOCB **pacb;
>
> ret = qemu_paio_cancel(acb->aiocb.aio_fildes, &acb->aiocb);
> if (ret == QEMU_PAIO_NOTCANCELED) {
> @@ -673,18 +690,7 @@ static void raw_aio_cancel(BlockDriverAIOCB *blockacb)
> while (qemu_paio_error(&acb->aiocb) == EINPROGRESS);
> }
>
> - /* remove the callback from the queue */
> - pacb = &posix_aio_state->first_aio;
> - for(;;) {
> - if (*pacb == NULL) {
> - break;
> - } else if (*pacb == acb) {
> - *pacb = acb->next;
> - qemu_aio_release(acb);
> - break;
> - }
> - pacb = &acb->next;
> - }
> + raw_aio_remove(acb);
> }
> #else /* CONFIG_AIO */
> static int posix_aio_init(void)
>
>
>
>
prev parent reply other threads:[~2009-01-29 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 14:40 [Qemu-devel] [PATCH] fix raw_aio_read\write error handling Stefano Stabellini
2009-01-29 17:02 ` Anthony Liguori [this message]
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=4981E13F.5010700@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.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).