Fix: Ensure that unbound Netlink sockets are bound when sending a message. #11961
Conversation
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
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?s=60&v=4){kind=small}
copybara-service
bot
force-pushed
the
test/cl786348487
branch
from
8b3c41f to
65f9514
Compare
…sage. If a Netlink socket is not bound when a message is sent through it, it should automatically be bound to assign it a unique portID. This becomes relevant in cases where the portId is used for access verification, such as for table owners in NETLINK_NETFILTER sockets. PiperOrigin-RevId: 786348487
copybara-service
bot
force-pushed
the
test/cl786348487
branch
from
65f9514 to
792bb9e
Compare
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.
Fix: Ensure that unbound Netlink sockets are bound when sending a message.
If a Netlink socket is not bound when a message is sent through it, it should
automatically be bound to assign it a unique portID. This becomes relevant
in cases where the portId is used for access verification, such as for
table owners in NETLINK_NETFILTER sockets.