Paolo Abeni 9d6ca4d88e vsock: cope with memory allocation failure at socket creation time ... [ Upstream commit 225d9464268599a5b4d094d02ec17808e44c7553 ] In the unlikely event that the kmalloc call in vmci_transport_socket_init() fails, we end-up calling vmci_transport_destruct() with a NULL vmci_trans() and oopsing. This change addresses the above explicitly checking for zero vmci_trans() at destruction time. Reported-by: Xiumei Mu <xmu@redhat.com> Fixes: d021c34405 ("VSOCK: Introduce VM Sockets") Signed-off-by: Paolo Abeni <pabeni@redhat.com> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com> Reviewed-by: Jorgen Hansen <jhansen@vmware.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Sasha Levin <sashal@kernel.org>		2019-02-23 09:05:13 +01:00
..
af_vsock.c	vsock: split dwork to avoid reinitializations	2018-08-22 07:48:35 +02:00
Kconfig
Makefile
vmci_transport.c	vsock: cope with memory allocation failure at socket creation time	2019-02-23 09:05:13 +01:00
vmci_transport.h	VSOCK: sock_put wasn't safe to call in interrupt context	2015-10-22 07:21:05 -07:00
vmci_transport_notify.c	net: Fix use after free by removing length arg from sk_data_ready callbacks.	2014-04-11 16:15:36 -04:00
vmci_transport_notify.h
vmci_transport_notify_qstate.c	net: Fix use after free by removing length arg from sk_data_ready callbacks.	2014-04-11 16:15:36 -04:00
vsock_addr.c