Shuhei Matsumoto 07ae9b780e sock/posix: Add MSG_NOSIGNAL to prevent SIGPIPE for a socket that may be closed ... We try avoiding write a closed socket by checking if the return value of recv() is zero. However it is not possible to completely avoid writing a socket which is already closed by the target. Repeatedly adding/removing listener in the NVMe-oF TCP target caused SIGPIPE to the NVMe-oF initiator. Fix the issue by adding MSG_NOSIGINAL to the flag of sendmsg(). Signed-off-by: Shuhei Matsumoto <smatsumoto@nvidia.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12119 (master) (cherry picked from commit 5fd1f68b63) Change-Id: I273679c91c4b867792e966b1dc2121f6d2188f16 Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12480 Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>		2022-06-30 13:32:31 -04:00
..
posix	sock/posix: Add MSG_NOSIGNAL to prevent SIGPIPE for a socket that may be closed	2022-06-30 13:32:31 -04:00
uring	uring: fix heap-use-after-free bug in sock_flush_client	2022-06-30 13:32:31 -04:00
Makefile	sock/vpp: remove VPP implementation	2020-08-17 08:19:46 +00:00
sock_kernel.h	uring: Not enable zero copy if fd is opened on a loopback device.	2021-08-13 07:14:38 +00:00