Patch "vhost/vsock: handle vhost_vq_init_access() error" has been added to the 4.9-stable tree
Subsystems (3)
This is a note to let you know that I've just added the patch titled
vhost/vsock: handle vhost_vq_init_access() error
to the 4.9-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
vhost-vsock-handle-vhost_vq_init_access-error.patch
and it can be found in the queue-4.9 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From foo@baz Thu Jun 15 16:23:30 CEST 2017
From: Stefan Hajnoczi <[email protected]>
Date: Thu, 19 Jan 2017 10:43:53 +0000
Subject: vhost/vsock: handle vhost_vq_init_access() error
From: Stefan Hajnoczi <[email protected]>
[ Upstream commit 0516ffd88fa0d006ee80389ce14a9ca5ae45e845 ]
Propagate the error when vhost_vq_init_access() fails and set vq->private_data to NULL.
--- drivers/vhost/vsock.c | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-)
drivers/vhost/vsock.c +9 -4
@@ -368,6 +368,7 @@ static void vhost_vsock_handle_rx_kick(sstatic int vhost_vsock_start (struct vhost_vsock *vsock) { +struct vhost_virtqueue *vq;size_t i;int ret;
@@ -378,19 +379,20 @@ static int vhost_vsock_start(struct vhos goto err;for (i =0 ; i <ARRAY_SIZE (vsock->vqs); i++) { -struct vhost_virtqueue *vq = &vsock->vqs[i]; + vq = &vsock->vqs[i];mutex_lock (&vq->mutex);if (!vhost_vq_access_ok (vq)) { ret = -EFAULT ; -mutex_unlock (&vq->mutex); goto err_vq; }if (!vq->private_data) { vq->private_data = vsock; -vhost_vq_init_access (vq); + ret =vhost_vq_init_access (vq); +if (ret) + goto err_vq; }mutex_unlock (&vq->mutex);
@@ -400,8 +402,11 @@ static int vhost_vsock_start(struct vhosreturn 0 ; err_vq: + vq->private_data =NULL ; +mutex_unlock (&vq->mutex); +for (i =0 ; i <ARRAY_SIZE (vsock->vqs); i++) { -struct vhost_virtqueue *vq = &vsock->vqs[i]; + vq = &vsock->vqs[i];mutex_lock (&vq->mutex); vq->private_data =NULL ;
Patches currently in stable-queue which might be from [email protected] are
queue-4.9/vhost-vsock-handle-vhost_vq_init_access-error.patch