[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190528105623.27983-1-sgarzare@redhat.com>
Date: Tue, 28 May 2019 12:56:19 +0200
From: Stefano Garzarella <sgarzare@...hat.com>
To: netdev@...r.kernel.org
Cc: linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, kvm@...r.kernel.org,
Stefan Hajnoczi <stefanha@...hat.com>,
"David S. Miller" <davem@...emloft.net>,
"Michael S . Tsirkin" <mst@...hat.com>
Subject: [PATCH 0/4] vsock/virtio: several fixes in the .probe() and .remove()
During the review of "[PATCH] vsock/virtio: Initialize core virtio vsock
before registering the driver", Stefan pointed out some possible issues
in the .probe() and .remove() callbacks of the virtio-vsock driver.
This series tries to solve these issues:
- Patch 1 postpones the 'the_virtio_vsock' assignment at the end of the
.probe() to avoid that some sockets queue works when the initialization
is not finished.
- Patches 2 and 3 stop workers before to call vdev->config->reset(vdev) to
be sure that no one is accessing the device, and adds another flush at the
end of the .remove() to avoid use after free.
- Patch 4 free also used buffers in the virtqueues during the .remove().
Stefano Garzarella (4):
vsock/virtio: fix locking around 'the_virtio_vsock'
vsock/virtio: stop workers during the .remove()
vsock/virtio: fix flush of works during the .remove()
vsock/virtio: free used buffers during the .remove()
net/vmw_vsock/virtio_transport.c | 105 ++++++++++++++++++++++++++-----
1 file changed, 90 insertions(+), 15 deletions(-)
--
2.20.1
Powered by blists - more mailing lists