Stefano Garzarella e226121fcc vsock/virtio: fix flush of works during the .remove() ... This patch moves the flush of works after vdev->config->del_vqs(vdev), because we need to be sure that no workers run before to free the 'vsock' object. Since we stopped the workers using the [tx|rx|event]_run flags, we are sure no one is accessing the device while we are calling vdev->config->reset(vdev), so we can safely move the workers' flush. Before the vdev->config->del_vqs(vdev), workers can be scheduled by VQ callbacks, so we must flush them after del_vqs(), to avoid use-after-free of 'vsock' object. Suggested-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Stefano Garzarella <sgarzare@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2019-07-08 15:35:17 -07:00
..
af_vsock_tap.c
af_vsock.c	Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net	2019-06-17 20:20:36 -07:00
diag.c
hyperv_transport.c	Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net	2019-06-22 08:59:24 -04:00
Kconfig
Makefile
virtio_transport_common.c	SPDX update for 5.2-rc6	2019-06-21 09:58:42 -07:00
virtio_transport.c	vsock/virtio: fix flush of works during the .remove()	2019-07-08 15:35:17 -07:00
vmci_transport_notify_qstate.c
vmci_transport_notify.c
vmci_transport_notify.h
vmci_transport.c
vmci_transport.h
vsock_addr.c