prov/util: Fix flag initialization for generic receive of unexpected entry #10741
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
…entry Signed-off-by: Steven Dashevsky <[email protected]>
aingerson
approved these changes
Jan 30, 2025
j-xiong
approved these changes
Jan 30, 2025
|
bot:aws:retest |
|
aws ci failure was a transient issue and irrelevant |
|
The remaining CI failure is with oneCCL over tcp, which is known issue and unrelated to this PR. |
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.
The flags that are passed to util_init_rx_entry when called from util_srx_generic_trecv are not OR'ed with FI_TAGGED | FI_RECV. The function util_srx_generic_trecv is also called in a different flow from util_get_recv_entry with the flags OR'ed (working flow). The same issue is present in the util_srx_generic_recv function but instead of FI_TAGGED it should be FI_MSG.