VSOCK: do not disconnect socket when peer has shutdown SEND only
authorIan Campbell <ian.campbell@docker.com>
Wed, 4 May 2016 13:21:53 +0000 (14:21 +0100)
committerDavid S. Miller <davem@davemloft.net>
Fri, 6 May 2016 03:31:29 +0000 (23:31 -0400)
commitdedc58e067d8c379a15a8a183c5db318201295bb
tree208d9904d31d38e55ae69b8dfff5c693cc428f72
parent82d69203df634b4dfa765c94f60ce9482bcc44d6
VSOCK: do not disconnect socket when peer has shutdown SEND only

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>
net/vmw_vsock/af_vsock.c
This page took 0.026007 seconds and 5 git commands to generate.