diff options
author | Dave Martin <Dave.Martin@arm.com> | 2019-06-06 11:58:07 +0100 |
---|---|---|
committer | Marc Zyngier <marc.zyngier@arm.com> | 2019-06-12 15:54:41 +0100 |
commit | 4729ec8c1e1145234aeeebad5d96d77f4ccbb00a (patch) | |
tree | 7e22e84c44d61a3c703b22e7cd4b783b51005d40 /virt | |
parent | df205b5c63281e4f32caac22adda18fd68795e80 (diff) | |
download | linux-stable-4729ec8c1e1145234aeeebad5d96d77f4ccbb00a.tar.gz linux-stable-4729ec8c1e1145234aeeebad5d96d77f4ccbb00a.tar.bz2 linux-stable-4729ec8c1e1145234aeeebad5d96d77f4ccbb00a.zip |
KVM: arm/arm64: vgic: Fix kvm_device leak in vgic_its_destroy
kvm_device->destroy() seems to be supposed to free its kvm_device
struct, but vgic_its_destroy() is not currently doing this,
resulting in a memory leak, resulting in kmemleak reports such as
the following:
unreferenced object 0xffff800aeddfe280 (size 128):
comm "qemu-system-aar", pid 13799, jiffies 4299827317 (age 1569.844s)
[...]
backtrace:
[<00000000a08b80e2>] kmem_cache_alloc+0x178/0x208
[<00000000dcad2bd3>] kvm_vm_ioctl+0x350/0xbc0
Fix it.
Cc: Andre Przywara <andre.przywara@arm.com>
Fixes: 1085fdc68c60 ("KVM: arm64: vgic-its: Introduce new KVM ITS device")
Signed-off-by: Dave Martin <Dave.Martin@arm.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'virt')
-rw-r--r-- | virt/kvm/arm/vgic/vgic-its.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/virt/kvm/arm/vgic/vgic-its.c b/virt/kvm/arm/vgic/vgic-its.c index 44ceaccb18cf..8c9fe831bce4 100644 --- a/virt/kvm/arm/vgic/vgic-its.c +++ b/virt/kvm/arm/vgic/vgic-its.c @@ -1734,6 +1734,7 @@ static void vgic_its_destroy(struct kvm_device *kvm_dev) mutex_unlock(&its->its_lock); kfree(its); + kfree(kvm_dev);/* alloc by kvm_ioctl_create_device, free by .destroy */ } static int vgic_its_has_attr_regs(struct kvm_device *dev, |