From: Kevin Wolf <kwolf@redhat.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com,
stefano.stabellini@eu.citrix.com
Subject: Re: [Qemu-devel] [PATCH v2] xen_disk: fix io accounting
Date: Fri, 7 Feb 2014 17:17:45 +0100 [thread overview]
Message-ID: <20140207161745.GC9796@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1391784474-418-1-git-send-email-olaf@aepfle.de>
Am 07.02.2014 um 15:47 hat Olaf Hering geschrieben:
> bdrv_acct_done was called unconditional. But in case the ioreq has no
> segments there is no matching bdrv_acct_start call. This could lead to
> bogus accounting values.
>
> Found by code inspection.
>
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
> ---
> v2:
> add comment /* fall through */
>
> hw/block/xen_disk.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/hw/block/xen_disk.c b/hw/block/xen_disk.c
> index 098f6c6..fb4ca4a 100644
> --- a/hw/block/xen_disk.c
> +++ b/hw/block/xen_disk.c
> @@ -483,7 +483,19 @@ static void qemu_aio_complete(void *opaque, int ret)
> ioreq->status = ioreq->aio_errors ? BLKIF_RSP_ERROR : BLKIF_RSP_OKAY;
> ioreq_unmap(ioreq);
> ioreq_finish(ioreq);
> - bdrv_acct_done(ioreq->blkdev->bs, &ioreq->acct);
> + switch (ioreq->req.operation) {
> + case BLKIF_OP_WRITE:
> + case BLKIF_OP_FLUSH_DISKCACHE:
> + if (!ioreq->req.nr_segments) {
> + break;
> + }
> + /* fall through */
> + case BLKIF_OP_READ:
> + bdrv_acct_done(ioreq->blkdev->bs, &ioreq->acct);
> + break;
> + default:
> + break;
> + }
> qemu_bh_schedule(ioreq->blkdev->bh);
> }
I think the default case could actually be abort() because it should
never happen. But either way, you can add:
Acked-by: Kevin Wolf <kwolf@redhat.com>
prev parent reply other threads:[~2014-02-07 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 14:47 [Qemu-devel] [PATCH v2] xen_disk: fix io accounting Olaf Hering
2014-02-07 14:57 ` Stefano Stabellini
2014-02-07 15:03 ` Olaf Hering
2014-02-07 16:17 ` Kevin Wolf [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=20140207161745.GC9796@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=olaf@aepfle.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=stefano.stabellini@eu.citrix.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).