From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: peter.maydell@linaro.org, famz@redhat.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
qemu-stable@nongnu.org, qemu-devel@nongnu.org,
aliguori@amazon.com
Subject: Re: [Qemu-devel] [2.2 PATCH V2] virtio-net: fix unmap leak
Date: Thu, 27 Nov 2014 14:33:41 +0200 [thread overview]
Message-ID: <20141127123341.GC13476@redhat.com> (raw)
In-Reply-To: <1417082643-23907-1-git-send-email-jasowang@redhat.com>
On Thu, Nov 27, 2014 at 06:04:03PM +0800, Jason Wang wrote:
> virtio_net_handle_ctrl() and other functions that process control vq
> request call iov_discard_front() which will shorten the iov. This will
> lead unmapping in virtqueue_push() leaks mapping.
>
> Fixes this by keeping the original iov untouched and using a temp variable
> in those functions.
>
> Cc: Wen Congyang <wency@cn.fujitsu.com>
> Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Jason Wang <jasowang@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Peter, can you pick this up or do you want a pull request?
> ---
> Changes from V1:
> - Use g_memdup() to simplify codes
> ---
> hw/net/virtio-net.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
> index 9b88775..e574bd4 100644
> --- a/hw/net/virtio-net.c
> +++ b/hw/net/virtio-net.c
> @@ -798,7 +798,7 @@ static void virtio_net_handle_ctrl(VirtIODevice *vdev, VirtQueue *vq)
> virtio_net_ctrl_ack status = VIRTIO_NET_ERR;
> VirtQueueElement elem;
> size_t s;
> - struct iovec *iov;
> + struct iovec *iov, *iov2;
> unsigned int iov_cnt;
>
> while (virtqueue_pop(vq, &elem)) {
> @@ -808,8 +808,8 @@ static void virtio_net_handle_ctrl(VirtIODevice *vdev, VirtQueue *vq)
> exit(1);
> }
>
> - iov = elem.out_sg;
> iov_cnt = elem.out_num;
> + iov2 = iov = g_memdup(elem.out_sg, sizeof(struct iovec) * elem.out_num);
> s = iov_to_buf(iov, iov_cnt, 0, &ctrl, sizeof(ctrl));
> iov_discard_front(&iov, &iov_cnt, sizeof(ctrl));
> if (s != sizeof(ctrl)) {
> @@ -833,6 +833,7 @@ static void virtio_net_handle_ctrl(VirtIODevice *vdev, VirtQueue *vq)
>
> virtqueue_push(vq, &elem, sizeof(status));
> virtio_notify(vdev, vq);
> + g_free(iov2);
> }
> }
>
> --
> 1.9.1
next prev parent reply other threads:[~2014-11-27 12:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 10:04 [Qemu-devel] [2.2 PATCH V2] virtio-net: fix unmap leak Jason Wang
2014-11-27 10:28 ` Stefano Stabellini
2014-11-27 10:31 ` Fam Zheng
2014-11-27 12:33 ` Michael S. Tsirkin [this message]
2014-11-27 12:42 ` Peter Maydell
2014-11-27 12:46 ` [Qemu-devel] [2.2 PATCH V2 for-4.5] " Stefano Stabellini
2014-11-27 14:09 ` [Qemu-devel] [2.2 PATCH V2] " Peter Maydell
2014-11-27 14:45 ` Michael S. Tsirkin
2014-11-27 14:54 ` Stefano Stabellini
2014-11-27 15:03 ` Michael S. Tsirkin
2014-11-27 16:40 ` Michael S. Tsirkin
2014-11-28 13:05 ` Peter Maydell
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=20141127123341.GC13476@redhat.com \
--to=mst@redhat.com \
--cc=aliguori@amazon.com \
--cc=famz@redhat.com \
--cc=jasowang@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stefano.stabellini@eu.citrix.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).