From: Paolo Bonzini <pbonzini@redhat.com>
To: Jing Zhang <jingzhangos@google.com>,
Pavel Skripkin <paskripkin@gmail.com>
Cc: KVM <kvm@vger.kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH next] kvm: debugfs: fix memory leak in kvm_create_vm_debugfs
Date: Thu, 8 Jul 2021 18:58:53 +0200 [thread overview]
Message-ID: <0b028e3d-d363-05cd-3dc3-8ccc5704ae1c@redhat.com> (raw)
In-Reply-To: <CAAdAUtiAA+H178X7pU1KLzKwmPZ1jTOUpmsP0TvFzqVH5gJAdg@mail.gmail.com>
On 01/07/21 23:24, Jing Zhang wrote:
> In commit bc9e9e672df9 ("KVM: debugfs: Reuse binary stats descriptors")
> loop for filling debugfs_stat_data was copy-pasted 2 times, but
> in the second loop pointers are saved over pointers allocated
> in the first loop. It causes memory leak. Fix it.
>
> Fixes: bc9e9e672df9 ("KVM: debugfs: Reuse binary stats descriptors")
> Signed-off-by: Pavel Skripkin<paskripkin@gmail.com>
> ---
Queued, thanks.
Paolo
prev parent reply other threads:[~2021-07-08 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 19:55 [PATCH next] kvm: debugfs: fix memory leak in kvm_create_vm_debugfs Pavel Skripkin
2021-07-01 21:24 ` Jing Zhang
2021-07-08 16:58 ` Paolo Bonzini [this message]
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=0b028e3d-d363-05cd-3dc3-8ccc5704ae1c@redhat.com \
--to=pbonzini@redhat.com \
--cc=jingzhangos@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paskripkin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.