From: Michael S. Tsirkin Date: Sun, 4 Jan 2015 15:28:27 +0000 (+0200) Subject: virtio_pci: document why we defer kfree X-Git-Tag: v3.16.35~2830 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=ae4aaf8706bc401d8426e96485322deaa92801cb;p=thirdparty%2Fkernel%2Fstable.git virtio_pci: document why we defer kfree commit a1eb03f546d651a8f39c7d0692b1f7f5b4e7e3cd upstream. The reason we defer kfree until release function is because it's a general rule for kobjects: kfree of the reference counter itself is only legal in the release function. Previous patch didn't make this clear, document this in code. Signed-off-by: Michael S. Tsirkin [ luis: backported to 3.16: - file rename: virtio_pci_legacy.c -> virtio_pci.c ] Signed-off-by: Luis Henriques --- diff --git a/drivers/virtio/virtio_pci.c b/drivers/virtio/virtio_pci.c index a46570005a987..52c4607fec9e4 100644 --- a/drivers/virtio/virtio_pci.c +++ b/drivers/virtio/virtio_pci.c @@ -671,6 +671,9 @@ static void virtio_pci_release_dev(struct device *_d) struct virtio_device *vdev = dev_to_virtio(_d); struct virtio_pci_device *vp_dev = to_vp_device(vdev); + /* As struct device is a kobject, it's not safe to + * free the memory (including the reference counter itself) + * until it's release callback. */ kfree(vp_dev); }