ovs: don't allow peers with the same name #353
Merged
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
slyon
approved these changes
May 1, 2023
daniloegea
force-pushed
the
fix_ovs_ports_same_name
branch
from
May 1, 2023 14:21
70ac977 to
57a711f
Compare
daniloegea
force-pushed
the
fix_ovs_ports_same_name
branch
from
May 1, 2023 16:43
57a711f to
0872b17
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.
I found it thanks to a memory leak. If both peers have the same name, the netdef will end up with a
netdef->peer_linkpointing to itself andnetdef->linkstrdup'ed twice.Description
Checklist
make checksuccessfully.make check-coverage).