All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Honig <ahonig@google.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCHv2] KVM: x86: Fix memory leak in vmx.c
Date: Thu, 18 Apr 2013 10:20:05 +0200	[thread overview]
Message-ID: <516FACB5.2040000@redhat.com> (raw)
In-Reply-To: <CAKB9nXvH5v+z=J0xN4Go_9YLK3ZKj8y-XveREjxKgVOsuyfHXw@mail.gmail.com>

Il 18/04/2013 01:03, Andrew Honig ha scritto:
> I don't have a significant objection to freeing the memory in
> kvm_arch_free_memslot, although I think it's a little harder to
> understand.  I like the idea of being symmetric (memory is allocated
> by calling kvm_set_memory_region and freed using the same technique).
> That way if someone changes from vm_mmap to something else it will be
> obvious that they need to change both.
> 
> Also, it looks like your patch is based on something several commits
> behind HEAD on virt/kvm/kvm.git,

Yeah, it was just whatever version I had checked out on the laptop. :)
So that maintainers can look at both approaches and see what they prefer.

Gleb, Marcelo, wdyt?

Paolo

> which significantly affect your
> patch.  In the HEAD version it assumes that user_alloc is always set
> unless it's a private memslot.  This appears to already have been the
> case and allows a bunch of simplifications, some of which would apply
> to your patch.


  reply	other threads:[~2013-04-18  8:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 17:54 [PATCHv2] KVM: x86: Fix memory leak in vmx.c Andrew Honig
2013-04-17 20:37 ` Eric Northup
2013-04-17 21:55 ` Paolo Bonzini
2013-04-17 23:03   ` Andrew Honig
2013-04-18  8:20     ` Paolo Bonzini [this message]
2013-04-18  8:50       ` Gleb Natapov
2013-04-18 10:21 ` Gleb Natapov

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=516FACB5.2040000@redhat.com \
    --to=pbonzini@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 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.