From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Vivek Kasireddy <vivek.kasireddy@intel.com>, qemu-devel@nongnu.org
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [RFC PATCH] hw/display/virtio-gpu: Fix memory leak (CID 1453811)
Date: Mon, 14 Jun 2021 12:52:43 +0200 [thread overview]
Message-ID: <e69a7f99-7d35-12f8-21af-48cc95172e6d@redhat.com> (raw)
In-Reply-To: <20210531101928.1662732-1-philmd@redhat.com>
ping?
On 5/31/21 12:19 PM, Philippe Mathieu-Daudé wrote:
> To avoid leaking memory on the error path, reorder the
> code as:
> - check the parameters first
> - check resource already existing
> - finally allocate memory
>
> Reported-by: Coverity (CID 1453811: RESOURCE_LEAK)
> Fixes: e0933d91b1c ("virtio-gpu: Add virtio_gpu_resource_create_blob")
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> RFC because the s->iov check is dubious.
> ---
> hw/display/virtio-gpu.c | 28 +++++++++++-----------------
> 1 file changed, 11 insertions(+), 17 deletions(-)
>
> diff --git a/hw/display/virtio-gpu.c b/hw/display/virtio-gpu.c
> index 4d549377cbc..8d047007bbb 100644
> --- a/hw/display/virtio-gpu.c
> +++ b/hw/display/virtio-gpu.c
> @@ -340,8 +340,15 @@ static void virtio_gpu_resource_create_blob(VirtIOGPU *g,
> return;
> }
>
> - res = virtio_gpu_find_resource(g, cblob.resource_id);
> - if (res) {
> + if (cblob.blob_mem != VIRTIO_GPU_BLOB_MEM_GUEST &&
> + cblob.blob_flags != VIRTIO_GPU_BLOB_FLAG_USE_SHAREABLE) {
> + qemu_log_mask(LOG_GUEST_ERROR, "%s: invalid memory type\n",
> + __func__);
> + cmd->error = VIRTIO_GPU_RESP_ERR_INVALID_PARAMETER;
> + return;
> + }
> +
> + if (virtio_gpu_find_resource(g, cblob.resource_id)) {
> qemu_log_mask(LOG_GUEST_ERROR, "%s: resource already exists %d\n",
> __func__, cblob.resource_id);
> cmd->error = VIRTIO_GPU_RESP_ERR_INVALID_RESOURCE_ID;
> @@ -352,25 +359,12 @@ static void virtio_gpu_resource_create_blob(VirtIOGPU *g,
> res->resource_id = cblob.resource_id;
> res->blob_size = cblob.size;
>
> - if (cblob.blob_mem != VIRTIO_GPU_BLOB_MEM_GUEST &&
> - cblob.blob_flags != VIRTIO_GPU_BLOB_FLAG_USE_SHAREABLE) {
> - qemu_log_mask(LOG_GUEST_ERROR, "%s: invalid memory type\n",
> - __func__);
> - cmd->error = VIRTIO_GPU_RESP_ERR_INVALID_PARAMETER;
> - g_free(res);
> - return;
> - }
> -
> - if (res->iov) {
> - cmd->error = VIRTIO_GPU_RESP_ERR_UNSPEC;
> - return;
> - }
> -
> ret = virtio_gpu_create_mapping_iov(g, cblob.nr_entries, sizeof(cblob),
> cmd, &res->addrs, &res->iov,
> &res->iov_cnt);
> - if (ret != 0) {
> + if (ret != 0 || res->iov) {
> cmd->error = VIRTIO_GPU_RESP_ERR_UNSPEC;
> + g_free(res);
> return;
> }
>
>
next prev parent reply other threads:[~2021-06-14 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 10:19 [RFC PATCH] hw/display/virtio-gpu: Fix memory leak (CID 1453811) Philippe Mathieu-Daudé
2021-06-14 10:52 ` Philippe Mathieu-Daudé [this message]
2021-06-21 9:59 ` Philippe Mathieu-Daudé
2021-07-06 10:01 ` Philippe Mathieu-Daudé
2021-07-07 11:04 ` Marc-André Lureau
2021-07-14 7:43 ` Kasireddy, Vivek
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=e69a7f99-7d35-12f8-21af-48cc95172e6d@redhat.com \
--to=philmd@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vivek.kasireddy@intel.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).