diff options
| author | Stefano Garzarella <sgarzare@redhat.com> | 2019-02-01 12:42:06 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-03-13 14:02:36 -0700 |
| commit | cd2013568dd51c6fc364c6d876d0fc624446572c (patch) | |
| tree | c5ad1afdb46db6e1d58a5a84522d5f7cec29c23d /include/acpi | |
| parent | f3ffd4559de2479caad378912b2b52a761d8801b (diff) | |
| download | linux-stable-cd2013568dd51c6fc364c6d876d0fc624446572c.tar.gz linux-stable-cd2013568dd51c6fc364c6d876d0fc624446572c.tar.bz2 linux-stable-cd2013568dd51c6fc364c6d876d0fc624446572c.zip | |
vsock/virtio: fix kernel panic after device hot-unplug
[ Upstream commit 22b5c0b63f32568e130fa2df4ba23efce3eb495b ]
virtio_vsock_remove() invokes the vsock_core_exit() also if there
are opened sockets for the AF_VSOCK protocol family. In this way
the vsock "transport" pointer is set to NULL, triggering the
kernel panic at the first socket activity.
This patch move the vsock_core_init()/vsock_core_exit() in the
virtio_vsock respectively in module_init and module_exit functions,
that cannot be invoked until there are open sockets.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1609699
Reported-by: Yan Fu <yafu@redhat.com>
Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
Acked-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'include/acpi')
0 files changed, 0 insertions, 0 deletions