Commit 2020e4a1 authored May 14, 2025 by Jacek Kalwas Committed by Tomasz Zawadzki May 21, 2025

sock: clarify spdk_sock_writev on failure behavior



All SPDK in-tree usages check for EAGAIN errno on failure.
This is likely due to SSL implementation which defines set of retryable
errors.

Change-Id: Iae4667c78024e2ce2054c3c42b7a9e6f3ef3f44e
Signed-off-by: Jacek Kalwas <jacek.kalwas@nutanix.com>
Reviewed-on: https://review.spdk.io/c/spdk/spdk/+/25955


Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com>
Community-CI: Mellanox Build Bot
Reviewed-by: Ben Walker <ben@nvidia.com>
Reviewed-by: Jim Harris <jim.harris@nvidia.com>
Tested-by: SPDK Automated Test System <spdkbot@gmail.com>

parent 31d048ca

include/spdk/sock.h

+3 −1

Original line number	Diff line number	Diff line
		@@ -426,11 +426,13 @@ ssize_t spdk_sock_recv(struct spdk_sock sock, void buf, size_t len);
		/**
		* Write message to the given socket from the I/O vector array.
		*
		* On failure check errno matching EAGAIN to determine failure is retryable.
		*
		* \param sock Socket to write to.
		* \param iov I/O vector.
		* \param iovcnt Number of I/O vectors in the array.
		*
		* \return the length of written message on success, -1 on failure.
		* \return the length of written message on success, -1 on failure with errno set.
		*/
		ssize_t spdk_sock_writev(struct spdk_sock sock, struct iovec iov, int iovcnt);