From: Gleb Natapov <gleb@redhat.com>
To: Andrew Honig <ahonig@google.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCHv3] KVM: x86: Fix memory leak in vmx.c
Date: Mon, 22 Apr 2013 11:02:50 +0300 [thread overview]
Message-ID: <20130422080250.GJ8997@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1304180936160.2452@ahonig-virtual-machine>
On Thu, Apr 18, 2013 at 09:38:14AM -0700, Andrew Honig wrote:
>
> If userspace creates and destroys multiple VMs within the same process
> we leak 20k of memory in the userspace process context per VM. This
> patch frees the memory in kvm_arch_destroy_vm. If the process exits
> without closing the VM file descriptor or the file descriptor has been
> shared with another process then we don't free the memory.
>
> It's still possible for a user space process to leak memory if the last
> process to close the fd for the VM is not the process that created it.
> However, this is an unexpected case that's only caused by a user space
> process that's misbehaving.
>
> Signed-off-by: Andrew Honig <ahonig@google.com>
Applied, thanks.
> ---
> arch/x86/kvm/x86.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 8ffac42..3b389bf 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -6856,6 +6856,23 @@ void kvm_arch_sync_events(struct kvm *kvm)
>
> void kvm_arch_destroy_vm(struct kvm *kvm)
> {
> + if (current->mm == kvm->mm) {
> + /*
> + * Free memory regions allocated on behalf of userspace,
> + * unless the the memory map has changed due to process exit
> + * or fd copying.
> + */
> + struct kvm_userspace_memory_region mem;
> + memset(&mem, 0, sizeof(mem));
> + mem.slot = APIC_ACCESS_PAGE_PRIVATE_MEMSLOT;
> + kvm_set_memory_region(kvm, &mem);
> +
> + mem.slot = IDENTITY_PAGETABLE_PRIVATE_MEMSLOT;
> + kvm_set_memory_region(kvm, &mem);
> +
> + mem.slot = TSS_PRIVATE_MEMSLOT;
> + kvm_set_memory_region(kvm, &mem);
> + }
> kvm_iommu_unmap_guest(kvm);
> kfree(kvm->arch.vpic);
> kfree(kvm->arch.vioapic);
> --
> 1.7.10.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Gleb.
prev parent reply other threads:[~2013-04-22 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 16:38 [PATCHv3] KVM: x86: Fix memory leak in vmx.c Andrew Honig
2013-04-21 13:04 ` Gleb Natapov
2013-04-22 8:02 ` Gleb Natapov [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=20130422080250.GJ8997@redhat.com \
--to=gleb@redhat.com \
--cc=ahonig@google.com \
--cc=kvm@vger.kernel.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