Ian Campbell da6b6f3e3b VSOCK: do not disconnect socket when peer has shutdown SEND only ... [ Upstream commit dedc58e067 ] The peer may be expecting a reply having sent a request and then done a shutdown(SHUT_WR), so tearing down the whole socket at this point seems wrong and breaks for me with a client which does a SHUT_WR. Looking at other socket family's stream_recvmsg callbacks doing a shutdown here does not seem to be the norm and removing it does not seem to have had any adverse effects that I can see. I'm using Stefan's RFC virtio transport patches, I'm unsure of the impact on the vmci transport. Signed-off-by: Ian Campbell <ian.campbell@docker.com> Cc: "David S. Miller" <davem@davemloft.net> Cc: Stefan Hajnoczi <stefanha@redhat.com> Cc: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com> Cc: Andy King <acking@vmware.com> Cc: Dmitry Torokhov <dtor@vmware.com> Cc: Jorgen Hansen <jhansen@vmware.com> Cc: Adit Ranadive <aditr@vmware.com> Cc: netdev@vger.kernel.org Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2016-05-18 18:35:07 -07:00
..
af_vsock.c	VSOCK: do not disconnect socket when peer has shutdown SEND only	2016-05-18 18:35:07 -07:00
Kconfig	Revert "Merge branch 'vsock-virtio'"	2015-12-08 21:55:49 -05:00
Makefile	Revert "Merge branch 'vsock-virtio'"	2015-12-08 21:55:49 -05:00
vmci_transport_notify_qstate.c	VSOCK: constify vmci_transport_notify_ops structures	2015-11-23 15:49:29 -05:00
vmci_transport_notify.c	VSOCK: constify vmci_transport_notify_ops structures	2015-11-23 15:49:29 -05:00
vmci_transport_notify.h	VSOCK: constify vmci_transport_notify_ops structures	2015-11-23 15:49:29 -05:00
vmci_transport.c	VSOCK: call sk->sk_data_ready() on accept()	2015-11-04 22:03:10 -05:00
vmci_transport.h	VSOCK: constify vmci_transport_notify_ops structures	2015-11-23 15:49:29 -05:00
vsock_addr.c	VSOCK: Move af_vsock.h and vsock_addr.h to include/net	2013-07-27 22:14:06 -07:00