qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, pl@kamp.de, qemu-stable@nongnu.org,
	Stefan Hajnoczi <stefanha@redhat.com>,
	pbonzini@redhat.com, dgibson@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] virtio-blk: Fix double completion for werror=stop
Date: Mon, 16 Nov 2015 13:21:26 +0100	[thread overview]
Message-ID: <5649CA46.3090709@redhat.com> (raw)
In-Reply-To: <1447654236-2979-1-git-send-email-famz@redhat.com>



On 16/11/2015 07:10, Fam Zheng wrote:
> When a request R is absorbed by request M, it is appended to the
> "mr_next" queue led by M, and is completed together with the completion
> of M, in virtio_blk_rw_complete.
> 
> With error policy equals stop, if M has an I/O error, now R also gets
> prepended to the per device DMA restart queue, which will be retried
> when VM resumes.  It leads to a double completion (in symptoms of memory
> corruption or use after free).
> 
> Adding R to the queue is superfluous, only M needs to be in the queue.
> 
> Fix this by marking request R as "merged" and skipping it in
> virtio_blk_handle_rw_error.
> 
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Fam Zheng <famz@redhat.com>
> 
> ---
> 
> v2: Don't lose the request in migration. [Paolo]

Tested-by: Laurent Vivier <lvivier@redhat.com>


> ---
>  hw/block/virtio-blk.c          | 7 +++++++
>  include/hw/virtio/virtio-blk.h | 1 +
>  2 files changed, 8 insertions(+)
> 
> diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
> index e70fccf..5cdb06f 100644
> --- a/hw/block/virtio-blk.c
> +++ b/hw/block/virtio-blk.c
> @@ -36,6 +36,7 @@ VirtIOBlockReq *virtio_blk_alloc_request(VirtIOBlock *s)
>      req->in_len = 0;
>      req->next = NULL;
>      req->mr_next = NULL;
> +    req->merged = false;
>      return req;
>  }
>  
> @@ -344,6 +345,7 @@ static inline void submit_requests(BlockBackend *blk, MultiReqBuffer *mrb,
>          for (i = start + 1; i < start + num_reqs; i++) {
>              qemu_iovec_concat(qiov, &mrb->reqs[i]->qiov, 0,
>                                mrb->reqs[i]->qiov.size);
> +            mrb->reqs[i]->merged = true;
>              mrb->reqs[i - 1]->mr_next = mrb->reqs[i];
>              nb_sectors += mrb->reqs[i]->qiov.size / BDRV_SECTOR_SIZE;
>          }
> @@ -511,6 +513,11 @@ void virtio_blk_handle_request(VirtIOBlockReq *req, MultiReqBuffer *mrb)
>                - sizeof(struct virtio_blk_inhdr);
>      iov_discard_back(in_iov, &in_num, sizeof(struct virtio_blk_inhdr));
>  
> +    if (req->merged) {
> +        /* Enough for restarting a (migrated) merged request, no need to
> +         * actually submit I/O. */
> +        return;
> +    }
>      type = virtio_ldl_p(VIRTIO_DEVICE(req->dev), &req->out.type);
>  
>      /* VIRTIO_BLK_T_OUT defines the command direction. VIRTIO_BLK_T_BARRIER
> diff --git a/include/hw/virtio/virtio-blk.h b/include/hw/virtio/virtio-blk.h
> index 6bf5905..db4adf4 100644
> --- a/include/hw/virtio/virtio-blk.h
> +++ b/include/hw/virtio/virtio-blk.h
> @@ -70,6 +70,7 @@ typedef struct VirtIOBlockReq {
>      size_t in_len;
>      struct VirtIOBlockReq *next;
>      struct VirtIOBlockReq *mr_next;
> +    bool merged;
>      BlockAcctCookie acct;
>  } VirtIOBlockReq;
>  
> 

  reply	other threads:[~2015-11-16 12:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16  6:10 [Qemu-devel] [PATCH v2] virtio-blk: Fix double completion for werror=stop Fam Zheng
2015-11-16 12:21 ` Laurent Vivier [this message]
2015-11-17  6:58 ` Stefan Hajnoczi
2015-11-17  7:28   ` Fam Zheng
2015-11-17  9:30     ` Stefan Hajnoczi

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=5649CA46.3090709@redhat.com \
    --to=lvivier@redhat.com \
    --cc=dgibson@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=pl@kamp.de \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).