qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 3/3] virtio-blk: Treat read/write beyond end as invalid
Date: Fri, 6 Jun 2014 11:21:05 +0800	[thread overview]
Message-ID: <20140606032105.GC11403@T430.nay.redhat.com> (raw)
In-Reply-To: <1401970536-18019-4-git-send-email-armbru@redhat.com>

On Thu, 06/05 14:15, Markus Armbruster wrote:
> The block layer fails such reads and writes just fine.  However, they
> then get treated like valid operations that fail: the error action
> gets executed.  Unwanted; reporting the error to the guest is the only
> sensible action.
> 
> Reject them before passing them to the block layer.  This bypasses the
> error action and I/O accounting.
> 
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
>  hw/block/virtio-blk.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
> index 2c68d0d..0b38049 100644
> --- a/hw/block/virtio-blk.c
> +++ b/hw/block/virtio-blk.c
> @@ -284,12 +284,19 @@ static void virtio_blk_handle_flush(VirtIOBlockReq *req, MultiReqBuffer *mrb)
>  static bool virtio_blk_sect_range_ok(VirtIOBlock *dev,
>                                       uint64_t sector, size_t size)
>  {
> +    uint64_t nb_sectors = size >> BDRV_SECTOR_BITS;
> +    uint64_t total_sectors;
> +
>      if (sector & dev->sector_mask) {
>          return false;
>      }
>      if (size % dev->conf->logical_block_size) {
>          return false;
>      }
> +    bdrv_get_geometry(dev->bs, &total_sectors);
> +    if (sector > total_sectors || nb_sectors > total_sectors - sector) {
> +        return false;
> +    }
>      return true;
>  }
>  
> -- 
> 1.9.3
> 
> 

Reviewed-by: Fam Zheng <famz@redhat.com>

  reply	other threads:[~2014-06-06  3:21 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
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 [this message]
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=20140606032105.GC11403@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).