qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 1/3] block: Fix parameter checking in bdrv_co_copy_range_internal
Date: Mon, 2 Jul 2018 23:23:12 -0400	[thread overview]
Message-ID: <20180703032312.GA4184563@localhost.localdomain> (raw)
In-Reply-To: <20180703023758.14422-2-famz@redhat.com>

On Tue, Jul 03, 2018 at 10:37:56AM +0800, Fam Zheng wrote:
> src may be NULL if BDRV_REQ_ZERO_WRITE flag is set, in this case only
> check dst and dst->bs. This bug was introduced when moving in the
> request tracking code from bdrv_co_copy_range, in 37aec7d75eb.
> 
> This especially fixes the possible segfault when initializing src_bs
> with a NULL src.
> 
> Signed-off-by: Fam Zheng <famz@redhat.com>

Reviewed-by: Jeff Cody <jcody@redhat.com>

> ---
>  block/io.c | 29 +++++++++++++++--------------
>  1 file changed, 15 insertions(+), 14 deletions(-)
> 
> diff --git a/block/io.c b/block/io.c
> index 7035b78a20..b8845708d7 100644
> --- a/block/io.c
> +++ b/block/io.c
> @@ -2897,18 +2897,11 @@ static int coroutine_fn bdrv_co_copy_range_internal(BdrvChild *src,
>                                                      bool recurse_src)
>  {
>      BdrvTrackedRequest src_req, dst_req;
> -    BlockDriverState *src_bs = src->bs;
> -    BlockDriverState *dst_bs = dst->bs;
>      int ret;
>  
> -    if (!src || !dst || !src->bs || !dst->bs) {
> +    if (!dst || !dst->bs) {
>          return -ENOMEDIUM;
>      }
> -    ret = bdrv_check_byte_request(src->bs, src_offset, bytes);
> -    if (ret) {
> -        return ret;
> -    }
> -
>      ret = bdrv_check_byte_request(dst->bs, dst_offset, bytes);
>      if (ret) {
>          return ret;
> @@ -2917,16 +2910,24 @@ static int coroutine_fn bdrv_co_copy_range_internal(BdrvChild *src,
>          return bdrv_co_pwrite_zeroes(dst, dst_offset, bytes, flags);
>      }
>  
> +    if (!src || !src->bs) {
> +        return -ENOMEDIUM;
> +    }
> +    ret = bdrv_check_byte_request(src->bs, src_offset, bytes);
> +    if (ret) {
> +        return ret;
> +    }
> +
>      if (!src->bs->drv->bdrv_co_copy_range_from
>          || !dst->bs->drv->bdrv_co_copy_range_to
>          || src->bs->encrypted || dst->bs->encrypted) {
>          return -ENOTSUP;
>      }
> -    bdrv_inc_in_flight(src_bs);
> -    bdrv_inc_in_flight(dst_bs);
> -    tracked_request_begin(&src_req, src_bs, src_offset,
> +    bdrv_inc_in_flight(src->bs);
> +    bdrv_inc_in_flight(dst->bs);
> +    tracked_request_begin(&src_req, src->bs, src_offset,
>                            bytes, BDRV_TRACKED_READ);
> -    tracked_request_begin(&dst_req, dst_bs, dst_offset,
> +    tracked_request_begin(&dst_req, dst->bs, dst_offset,
>                            bytes, BDRV_TRACKED_WRITE);
>  
>      wait_serialising_requests(&src_req);
> @@ -2944,8 +2945,8 @@ static int coroutine_fn bdrv_co_copy_range_internal(BdrvChild *src,
>      }
>      tracked_request_end(&src_req);
>      tracked_request_end(&dst_req);
> -    bdrv_dec_in_flight(src_bs);
> -    bdrv_dec_in_flight(dst_bs);
> +    bdrv_dec_in_flight(src->bs);
> +    bdrv_dec_in_flight(dst->bs);
>      return ret;
>  }
>  
> -- 
> 2.17.1
> 

  reply	other threads:[~2018-07-03  3:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03  2:37 [Qemu-devel] [PATCH v4 0/3] backup: Use copy offloading Fam Zheng
2018-07-03  2:37 ` [Qemu-devel] [PATCH v4 1/3] block: Fix parameter checking in bdrv_co_copy_range_internal Fam Zheng
2018-07-03  3:23   ` Jeff Cody [this message]
2018-07-03  2:37 ` [Qemu-devel] [PATCH v4 2/3] block: Honour BDRV_REQ_NO_SERIALISING in copy range Fam Zheng
2018-07-03  2:37 ` [Qemu-devel] [PATCH v4 3/3] backup: Use copy offloading Fam Zheng
2018-07-03  3:25 ` [Qemu-devel] [PATCH v4 0/3] " Jeff Cody

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=20180703032312.GA4184563@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).