qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] kvm: fix memory leak on failure to read stats descriptors
Date: Mon, 5 Sep 2022 11:56:58 +0100	[thread overview]
Message-ID: <1554c88e-f4a7-b1ef-636e-31f77146b9f3@linaro.org> (raw)
In-Reply-To: <20220905100621.18289-1-pbonzini@redhat.com>

On 9/5/22 11:06, Paolo Bonzini wrote:
> Reported by Coverity as CID 1490142.
> 
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>   accel/kvm/kvm-all.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
> index 7c8ce18bdd..208b0c74e3 100644
> --- a/accel/kvm/kvm-all.c
> +++ b/accel/kvm/kvm-all.c
> @@ -3962,6 +3962,7 @@ static StatsDescriptors *find_stats_descriptors(StatsTarget target, int stats_fd
>                      size_desc * kvm_stats_header->num_desc, ret);
>           g_free(descriptors);
>           g_free(kvm_stats_desc);
> +        g_free(kvm_stats_header);
>           return NULL;
>       }

kvm_stats_header should also be freed just above, in the other read failure if block.

Alternately, can StatsDescriptors be reorg'ed as

   typedef struct StatsDescriptors {

       const char *ident; /* cache key, currently the StatsTarget */

       struct kvm_stats_desc *kvm_stats_desc;

-     struct kvm_stats_header *kvm_stats_header;
+     struct kvm_stats_header kvm_stats_header;
       QTAILQ_ENTRY(StatsDescriptors) next;

   } StatsDescriptors;


since it appears that kvm_stats_header has the same lifetime as the descriptor, and is not 
variable sized, like kvm_stats_desc.


r~


  reply	other threads:[~2022-09-05 11:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 10:06 [PATCH] kvm: fix memory leak on failure to read stats descriptors Paolo Bonzini
2022-09-05 10:56 ` Richard Henderson [this message]
2022-09-05 10:59 ` Marc-André Lureau

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=1554c88e-f4a7-b1ef-636e-31f77146b9f3@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=pbonzini@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).