linux-kernel - Re: [KVM PATCH v3 1/3] kvm: fix potential coalesced

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 1 Jun 2009 10:06:13 -0700
From:	Chris Wright <chrisw@...s-sol.org>
To:	Gregory Haskins <ghaskins@...ell.com>
Cc:	avi@...hat.com, chrisw@...s-sol.org, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [KVM PATCH v3 1/3] kvm: fix potential coalesced_mmio leak on
	shutdown

* Gregory Haskins (ghaskins@...ell.com) wrote:
> It would appear that we are invoking kfree() on the wrong pointer in the
> destructor for the coalesced_mmio device.  This could result in a potential
> leak during shutdown.  This works today because the kvm_io_device is
> the first element of the private structure, but this could change in
> the future, so lets clean this up.
> 
> Signed-off-by: Gregory Haskins <ghaskins@...ell.com>

Acked-by: Chris Wright <chrisw@...s-sol.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/