From: Chris Wright <chrisw@sous-sol.org>
To: Gregory Haskins <gregory.haskins@gmail.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Gregory Haskins <ghaskins@novell.com>,
avi@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kvm: fix coalesced_mmio leak on shutdown
Date: Wed, 27 May 2009 13:35:40 -0700 [thread overview]
Message-ID: <20090527203540.GJ20823@sequoia.sous-sol.org> (raw)
In-Reply-To: <4A1DA361.6050303@gmail.com>
* Gregory Haskins (gregory.haskins@gmail.com) wrote:
> Chris Wright wrote:
> > * Gregory Haskins (ghaskins@novell.com) wrote:
> >> It would appear that we are invoking kfree() on the wrong pointer in the
> >> destructor for the coalesced_mmio device. This would result in a potential
> >> leak during shutdown.
> >
> > Happens to work and not leak:
> >
> > struct kvm_coalesced_mmio_dev {
> > struct kvm_io_device dev;
> > struct kvm *kvm;
> > int nb_zones;
> > struct kvm_coalesced_mmio_zone zone[KVM_COALESCED_MMIO_ZONE_MAX];
> > };
> >
> >
> Ah, yes. That explains it. Still sloppy, tho.
Definitely.
> >> static void coalesced_mmio_destructor(struct kvm_io_device *this)
> >> {
> >> - kfree(this);
> >> + struct kvm_coalesced_mmio_dev *dev =
> >> + (struct kvm_coalesced_mmio_dev *)this->private;
> >>
> >
> > I think container_of() makes more sense here.
>
> I was working on that patch when I noticed the "leak" above. Figured I
> should send the fix out first, in case my container_of patch is shot down.
>
> Just polishing it up now. Will send out soon.
Sounds good.
thanks,
-chris
prev parent reply other threads:[~2009-05-27 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 16:41 [PATCH] kvm: fix coalesced_mmio leak on shutdown Gregory Haskins
2009-05-27 20:29 ` Chris Wright
2009-05-27 20:32 ` Gregory Haskins
2009-05-27 20:35 ` Chris Wright [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=20090527203540.GJ20823@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=avi@redhat.com \
--cc=ghaskins@novell.com \
--cc=gregory.haskins@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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