[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGxU2F6-Pb0BjnRBrBatLuC-Xg7f_aJuidW-jiQR59ZTQ-j2=A@mail.gmail.com>
Date: Tue, 29 Jan 2019 16:33:58 +0100
From: Stefano Garzarella <sgarzare@...hat.com>
To: davem@...emloft.net, netdev@...r.kernel.org
Cc: Stefan Hajnoczi <stefanha@...hat.com>
Subject: Re: [PATCH RFC v2 0/2] vsock/virtio: fix issues on device hot-unplug
Kindly ping :)
On Fri, Jan 4, 2019 at 3:34 PM Stefano Garzarella <sgarzare@...hat.com> wrote:
>
> These patches try to handle the hot-unplug of vsock virtio transport device in
> a proper way.
>
> Maybe move the vsock_core_init()/vsock_core_exit() functions in the module_init
> and module_exit of vsock_virtio_transport module can't be the best way, but the
> architecture of vsock_core forces us to this approach for now.
>
> The vsock_core proto_ops expect a valid pointer to the transport device, so we
> can't call vsock_core_exit() until there are open sockets.
>
> Another (little more complex) approach during the device removal, could be to
> unregister the AF_VSOCK protocol, then reset all sockets and wait for their
> destruction. At this point, we can set the transport pointer to NULL.
>
> Any suggestions would be helpful.
>
> v1 -> v2:
> - Fixed commit message of patch 1.
>
> Stefano Garzarella (2):
> vsock/virtio: fix kernel panic after device hot-unplug
> vsock/virtio: reset connected sockets on device removal
>
> net/vmw_vsock/virtio_transport.c | 29 +++++++++++++++++++++--------
> 1 file changed, 21 insertions(+), 8 deletions(-)
>
> --
> 2.20.1
>
Powered by blists - more mailing lists