You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the function nvme_tcp_qpair_process_completions in the case the socket was closed the spdk_sock_flush will return a negative value and the code won't reach nvme_tcp_qpair_check_timeout, This prevents checking for timeouts on sent commands
Expected Behavior
nvme_tcp_qpair_check_timeout should be called when spdk_sock_flush fails.
Current Behavior
spdk_sock_flush returns before reaching nvme_tcp_qpair_check_timeout
Possible Solution
calling nvme_tcp_qpair_check_timeout if rc < 0
The text was updated successfully, but these errors were encountered:
Bug report
In the function nvme_tcp_qpair_process_completions in the case the socket was closed the spdk_sock_flush will return a negative value and the code won't reach nvme_tcp_qpair_check_timeout, This prevents checking for timeouts on sent commands
Expected Behavior
nvme_tcp_qpair_check_timeout should be called when spdk_sock_flush fails.
Current Behavior
spdk_sock_flush returns before reaching nvme_tcp_qpair_check_timeout
Possible Solution
calling nvme_tcp_qpair_check_timeout if rc < 0
The text was updated successfully, but these errors were encountered: