[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <73d486dd-17d9-a3b3-c1e9-39a1138c0084@redhat.com>
Date: Tue, 20 Jul 2021 14:28:24 +0800
From: Jason Wang <jasowang@...hat.com>
To: Xianting Tian <tianxianting.txt@...ux.alibaba.com>,
stefanha@...hat.com, sgarzare@...hat.com, davem@...emloft.net,
kuba@...nel.org
Cc: kvm@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
Xianting Tian <xianting.tian@...ux.alibaba.com>
Subject: Re: [PATCH] vsock/virtio: set vsock frontend ready in
virtio_vsock_probe()
在 2021/7/20 上午11:42, Xianting Tian 写道:
> From: Xianting Tian <xianting.tian@...ux.alibaba.com>
>
> Add the missed virtio_device_ready() to set vsock frontend ready.
>
> Signed-off-by: Xianting Tian <xianting.tian@...ux.alibaba.com>
> ---
> net/vmw_vsock/virtio_transport.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/net/vmw_vsock/virtio_transport.c b/net/vmw_vsock/virtio_transport.c
> index e0c2c992a..eb4c607c4 100644
> --- a/net/vmw_vsock/virtio_transport.c
> +++ b/net/vmw_vsock/virtio_transport.c
> @@ -637,6 +637,8 @@ static int virtio_vsock_probe(struct virtio_device *vdev)
> vdev->priv = vsock;
> rcu_assign_pointer(the_virtio_vsock, vsock);
>
> + virtio_device_ready(vdev);
> +
> mutex_unlock(&the_virtio_vsock_mutex);
It's better to do this after the mutex_lock().
Thanks
>
> return 0;
Powered by blists - more mailing lists