prov/tcp: implement FI_FIREWALL_ADDR for AV inserts #10724
Draft
+49
−22
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
ooststep
force-pushed
the
av-no-connect
branch
from
903879e to
0399693
Compare
shefty
reviewed
Jan 29, 2025
FI_FIREWALL_ADDR indicates to the provider that the inserted addresses may be restricted by a firewall Signed-off-by: Stephen Oost <stephen.oost@intel.com>
ooststep
force-pushed
the
av-no-connect
branch
from
0399693 to
fb9a9bb
Compare
ooststep
changed the title
shefty
reviewed
Feb 5, 2025
Signed-off-by: Stephen Oost <stephen.oost@intel.com>
ooststep
force-pushed
the
av-no-connect
branch
from
fb9a9bb to
e7b02ec
Compare
|
The latest changes look reasonable to me. |
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.
This PR introduces a new
fi_av_insertflag,FI_FIREWALL_ADDR, which indicates that an av insert should fail if there is not already an established connection to the peer and the provider has no means to circumvent the firewall. The PR also implements the functionality for the TCP provider (and RXM provider, though this is not the primary goal).I do still need to add a fabtest for the feature but wanted to push this up for initial review in the meantime.
resolves #10637
replaces #10534