UCP/RNDV: Fix releasing of local request ID when switching to RNDV AM (v1.10.x) #6117
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
brminich
approved these changes
Jan 12, 2021
yosefe
approved these changes
Jan 12, 2021
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@yosefe ok to merge? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Fix releasing of local request ID when switching to RNDV AM (backport of #6101)
Why ?
Fixes #6100 (comment)
When releasing local send request ID, need to use the
rndv_rtr_hdr->sreq_idinstead ofrndv_rtr_hdr->rreq_idwhich is saved tosreq->send.msg_proto.rreq_idwhen switiching to RNDV AM protocolHow ?
rndv_rtr_hdr->sreq_idinstead ofsreq->send.msg_proto.rreq_idat the end of the function when releasing local ID.