virtio_pci: defer kfree until release callback
authorSasha Levin <sasha.levin@oracle.com>
Fri, 2 Jan 2015 19:47:40 +0000 (14:47 -0500)
committerBen Hutchings <ben@decadent.org.uk>
Fri, 20 Feb 2015 00:49:34 +0000 (00:49 +0000)
commit119d5897cc5f9f73e352a1c647d21b9d506b8c0a
treee0592cfc58b11b686574140316d718cfad230eb6
parentddabe0f7922dc94249030ce3f3f7cae9ef34dbe3
virtio_pci: defer kfree until release callback

commit 63bd62a08ca45a0c804c3c89777edc7f76a2d6da upstream.

A struct device which has just been unregistered can live on past the
point at which a driver decides to drop it's initial reference to the
kobject gained on allocation.

This implies that when releasing a virtio device, we can't free a struct
virtio_device until the underlying struct device has been released,
which might not happen immediately on device_unregister().

Unfortunately, this is exactly what virtio pci does:
it has an empty release callback, and frees memory immediately
after unregistering the device.

This causes an easy to reproduce crash if CONFIG_DEBUG_KOBJECT_RELEASE
it enabled.

To fix, free the memory only once we know the device is gone in the release
callback.

Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
[bwh: Backported to 3.2: adjust filename]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
drivers/virtio/virtio_pci.c