Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nvme_tcp_qpair_check_timeout not called when spdk_sock_flush fails #2614

Closed
LiadOz opened this issue Aug 1, 2022 · 3 comments
Closed

nvme_tcp_qpair_check_timeout not called when spdk_sock_flush fails #2614

LiadOz opened this issue Aug 1, 2022 · 3 comments
Assignees
Labels

Comments

@LiadOz
Copy link
Contributor

LiadOz commented Aug 1, 2022

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

@LiadOz LiadOz added the Sighting label Aug 1, 2022
@jimharris
Copy link
Member

Hi @LiadOz,

I agree with your assessment on this - would you like to submit a patch for it? I'm happy to post one instead of you would prefer.

-Jim

@LiadOz
Copy link
Contributor Author

LiadOz commented Aug 2, 2022

I will submit a patch, thanks!

@tomzawadzki tomzawadzki added bug Medium Medium Priority Bug and removed Sighting labels Aug 9, 2022
@LiadOz
Copy link
Contributor Author

LiadOz commented Aug 12, 2022

patch is waiting for review https://review.spdk.io/gerrit/c/spdk/spdk/+/13891

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants