diff options
author | Ian Campbell <[email protected]> | 2016-05-04 14:21:53 +0100 |
---|---|---|
committer | David S. Miller <[email protected]> | 2016-05-05 23:31:29 -0400 |
commit | dedc58e067d8c379a15a8a183c5db318201295bb (patch) | |
tree | 208d9904d31d38e55ae69b8dfff5c693cc428f72 /tools/perf/util/trace-event-scripting.c | |
parent | 82d69203df634b4dfa765c94f60ce9482bcc44d6 (diff) |
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 <[email protected]>
Cc: "David S. Miller" <[email protected]>
Cc: Stefan Hajnoczi <[email protected]>
Cc: Claudio Imbrenda <[email protected]>
Cc: Andy King <[email protected]>
Cc: Dmitry Torokhov <[email protected]>
Cc: Jorgen Hansen <[email protected]>
Cc: Adit Ranadive <[email protected]>
Cc: [email protected]
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions