From: Fam Zheng <famz@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
uobergfe@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/3] virtio-blk: Bypass error action and I/O accounting on invalid r/w
Date: Fri, 6 Jun 2014 11:18:28 +0800 [thread overview]
Message-ID: <20140606031828.GB11403@T430.nay.redhat.com> (raw)
In-Reply-To: <1401970536-18019-3-git-send-email-armbru@redhat.com>
On Thu, 06/05 14:15, Markus Armbruster wrote:
> When a device model's I/O operation fails, we execute the error
> action. This lets layers above QEMU implement thin provisioning, or
> attempt to correct errors before they reach the guest. But when the
> I/O operation fails because its invalid, reporting the error to the
s/its/it's/ ?
Anyway,
Reviewed-by: Fam Zheng <famz@redhat.com>
> guest is the only sensible action.
>
> If the guest's read or write asks for an invalid sector range, fail
> the request right away, without considering the error action. No
> change with error action BDRV_ACTION_REPORT.
>
> Furthermore, bypass I/O accounting, because we want to track only I/O
> that actually reaches the block layer.
>
> The next commit will extend "invalid sector range" to cover attempts
> to read/write beyond the end of the medium.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> hw/block/virtio-blk.c | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
> index f2b4dca..2c68d0d 100644
> --- a/hw/block/virtio-blk.c
> +++ b/hw/block/virtio-blk.c
> @@ -300,15 +300,16 @@ static void virtio_blk_handle_write(VirtIOBlockReq *req, MultiReqBuffer *mrb)
>
> sector = ldq_p(&req->out->sector);
>
> - bdrv_acct_start(req->dev->bs, &req->acct, req->qiov.size, BDRV_ACCT_WRITE);
> -
> trace_virtio_blk_handle_write(req, sector, req->qiov.size / 512);
>
> if (!virtio_blk_sect_range_ok(req->dev, sector, req->qiov.size)) {
> - virtio_blk_rw_complete(req, -EIO);
> + virtio_blk_req_complete(req, VIRTIO_BLK_S_IOERR);
> + g_free(req);
> return;
> }
>
> + bdrv_acct_start(req->dev->bs, &req->acct, req->qiov.size, BDRV_ACCT_WRITE);
> +
> if (mrb->num_writes == 32) {
> virtio_submit_multiwrite(req->dev->bs, mrb);
> }
> @@ -330,14 +331,15 @@ static void virtio_blk_handle_read(VirtIOBlockReq *req)
>
> sector = ldq_p(&req->out->sector);
>
> - bdrv_acct_start(req->dev->bs, &req->acct, req->qiov.size, BDRV_ACCT_READ);
> -
> trace_virtio_blk_handle_read(req, sector, req->qiov.size / 512);
>
> if (!virtio_blk_sect_range_ok(req->dev, sector, req->qiov.size)) {
> - virtio_blk_rw_complete(req, -EIO);
> + virtio_blk_req_complete(req, VIRTIO_BLK_S_IOERR);
> + g_free(req);
> return;
> }
> +
> + bdrv_acct_start(req->dev->bs, &req->acct, req->qiov.size, BDRV_ACCT_READ);
> bdrv_aio_readv(req->dev->bs, sector, &req->qiov,
> req->qiov.size / BDRV_SECTOR_SIZE,
> virtio_blk_rw_complete, req);
> --
> 1.9.3
>
>
next prev parent reply other threads:[~2014-06-06 3:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 12:15 [Qemu-devel] [PATCH 0/3] virtio-blk: Suppress error action on r/w beyond end Markus Armbruster
2014-06-05 12:15 ` [Qemu-devel] [PATCH 1/3] virtio-blk: Factor common checks out of virtio_blk_handle_read/write() Markus Armbruster
2014-06-06 3:14 ` Fam Zheng
2014-06-05 12:15 ` [Qemu-devel] [PATCH 2/3] virtio-blk: Bypass error action and I/O accounting on invalid r/w Markus Armbruster
2014-06-06 3:18 ` Fam Zheng [this message]
2014-06-06 3:22 ` Eric Blake
2014-06-06 6:01 ` Markus Armbruster
2014-06-05 12:15 ` [Qemu-devel] [PATCH 3/3] virtio-blk: Treat read/write beyond end as invalid Markus Armbruster
2014-06-06 3:21 ` Fam Zheng
2014-06-20 4:16 ` Stefan Hajnoczi
2014-06-23 8:47 ` Markus Armbruster
2014-06-23 12:57 ` Markus Armbruster
2014-06-27 9:56 ` Stefan Hajnoczi
2014-06-06 7:36 ` [Qemu-devel] [PATCH 0/3] virtio-blk: Suppress error action on r/w beyond end Paolo Bonzini
2014-06-06 8:24 ` Markus Armbruster
2014-06-26 11:26 ` Markus Armbruster
2014-06-27 9:56 ` Stefan Hajnoczi
2014-07-01 8:57 ` Markus Armbruster
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=20140606031828.GB11403@T430.nay.redhat.com \
--to=famz@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=uobergfe@redhat.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).