prov/lnx: FI_CLAIM and FI_DISCARD fixes#11882
Merged
j-xiong merged 1 commit intoofiwg:mainfrom Feb 11, 2026
Merged
Conversation
When discarding or claiming a message, the entry should get removed from the unexpected queue so it can't be matched in the future. LNX has two paths for discarding - one with FI_PEEK and one with FI_CLAIM. The message needs to be discarded with the peer provider in both of these cases but discard_tag() was only getting called in one path. This adds the call to discard in the missing path Signed-off-by: Alexia Ingerson <alexia.ingerson@intel.com>
j-xiong
approved these changes
Feb 11, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When discarding or claiming a message, the entry should get removed from the unexpected queue so it can't be matched in the future.
LNX has two paths for discarding - one with FI_PEEK and one with FI_CLAIM. The message needs to be discarded with the peer provider in both of these cases but discard_tag() was only getting called in one path. This adds the call to discard in the missing path