bgpd: fix memory leak when reconfiguring a route distinguisher #17669
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
A memory leak happens when reconfiguring an already configured route distinguisher on an L3VPN BGP instance. Fix this by freeing the previous route distinguisher. Signed-off-by: Philippe Guibert <[email protected]>
ton31337
approved these changes
Dec 18, 2024
|
@Mergifyio backport stable/10.2 stable/10.1 stable/10.0 stable/9.1 stable/9.0 stable/8.5 |
✅ Backports have been created
|
This was referenced Dec 20, 2024
Jafaral
added a commit
that referenced
this pull request
Dec 20, 2024
bgpd: fix memory leak when reconfiguring a route distinguisher (backport #17669)
ton31337
added a commit
that referenced
this pull request
Dec 21, 2024
bgpd: fix memory leak when reconfiguring a route distinguisher (backport #17669)
ton31337
added a commit
that referenced
this pull request
Dec 21, 2024
bgpd: fix memory leak when reconfiguring a route distinguisher (backport #17669)
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.
A memory leak happens when reconfiguring an already configured route distinguisher on an L3VPN BGP instance. Fix this by freeing the previous route distinguisher.