| Message ID | 20200430024140.42065-1-justin.he@arm.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | vhost: add mutex_lock/unlock for vhost_vq_reset | expand |
diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index d450e16c5c25..622bfba2e5ab 100644 --- a/drivers/vhost/vhost.c +++ b/drivers/vhost/vhost.c @@ -297,6 +297,7 @@ static void vhost_vq_meta_reset(struct vhost_dev *d) static void vhost_vq_reset(struct vhost_dev *dev, struct vhost_virtqueue *vq) { + mutex_lock(&vq->mutex); vq->num = 1; vq->desc = NULL; vq->avail = NULL; @@ -323,6 +324,7 @@ static void vhost_vq_reset(struct vhost_dev *dev, vq->umem = NULL; vq->iotlb = NULL; __vhost_vq_meta_reset(vq); + mutex_unlock(&vq->mutex); } static int vhost_worker(void *data)
vq->mutex is to protect any vq accessing, hence adding mutex_lock/unlock makes sense to avoid potential race condition. Signed-off-by: Jia He <justin.he@arm.com> --- drivers/vhost/vhost.c | 2 ++ 1 file changed, 2 insertions(+)