qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Li Qiang <liq3ea@163.com>, mst@redhat.com
Cc: liq3ea@gmail.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] hw: virtio-mem: detach the element fromt the virtqueue when error occurs
Date: Thu, 13 Aug 2020 19:15:40 +0200	[thread overview]
Message-ID: <e3c0b22e-f8dc-b7ba-65f2-2cae488a41ce@redhat.com> (raw)
In-Reply-To: <20200813164637.58904-1-liq3ea@163.com>

On 13.08.20 18:46, Li Qiang wrote:

For now we use "virtio-mem:" for the subject, without the "hw: "part.

> If error occurs while processing the virtio request we should call
> 'virtqueue_detach_element' to detach the element from the virtqueue
> before free the elem.

What's the effect of this? In all cases we trigger a virtio_error(), so
do we really have to bother?

> 
> Signed-off-by: Li Qiang <liq3ea@163.com>
> ---
>  hw/virtio/virtio-mem.c | 13 +++++++------
>  1 file changed, 7 insertions(+), 6 deletions(-)
> 
> diff --git a/hw/virtio/virtio-mem.c b/hw/virtio/virtio-mem.c
> index 7740fc613f..5ac6c3ec67 100644
> --- a/hw/virtio/virtio-mem.c
> +++ b/hw/virtio/virtio-mem.c
> @@ -318,8 +318,7 @@ static void virtio_mem_handle_request(VirtIODevice *vdev, VirtQueue *vq)
>          if (iov_to_buf(elem->out_sg, elem->out_num, 0, &req, len) < len) {
>              virtio_error(vdev, "virtio-mem protocol violation: invalid request"
>                           " size: %d", len);
> -            g_free(elem);
> -            return;
> +            goto out_free;
>          }
>  
>          if (iov_size(elem->in_sg, elem->in_num) <
> @@ -327,8 +326,7 @@ static void virtio_mem_handle_request(VirtIODevice *vdev, VirtQueue *vq)
>              virtio_error(vdev, "virtio-mem protocol violation: not enough space"
>                           " for response: %zu",
>                           iov_size(elem->in_sg, elem->in_num));
> -            g_free(elem);
> -            return;
> +            goto out_free;
>          }
>  
>          type = le16_to_cpu(req.type);
> @@ -348,12 +346,15 @@ static void virtio_mem_handle_request(VirtIODevice *vdev, VirtQueue *vq)
>          default:
>              virtio_error(vdev, "virtio-mem protocol violation: unknown request"
>                           " type: %d", type);
> -            g_free(elem);
> -            return;
> +            goto out_free;
>          }
>  
>          g_free(elem);
>      }
> +
> +out_free:
> +    virtqueue_detach_element(vq, elem, 0);
> +    g_free(elem);
>  }
>  
>  static void virtio_mem_get_config(VirtIODevice *vdev, uint8_t *config_data)
> 


-- 
Thanks,

David / dhildenb



  reply	other threads:[~2020-08-13 17:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13 16:46 [PATCH] hw: virtio-mem: detach the element fromt the virtqueue when error occurs Li Qiang
2020-08-13 17:15 ` David Hildenbrand [this message]
2020-08-14  1:01   ` Li Qiang
2020-08-16 12:10     ` David Hildenbrand

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=e3c0b22e-f8dc-b7ba-65f2-2cae488a41ce@redhat.com \
    --to=david@redhat.com \
    --cc=liq3ea@163.com \
    --cc=liq3ea@gmail.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).