Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[action] [PR:17484] [FRR] Fix zebra memory leak when bgp fib suppress pending is enabled #17510

Merged
merged 1 commit into from
Dec 15, 2023

Conversation

mssonicbld
Copy link
Collaborator

Why I did it

Fix zebra leaking memory with fib suppress enabled. Porting the fix from
FRRouting/frr#14983

While running test_stress_route.py, systems with lower memory started to throw low memory logs. On further investigation, a memory leak has been found in zebra which was fixed in the FRR community.

Work item tracking
  • Microsoft ADO (number only):

How I did it

Creating patch for with the fix

How to verify it

Running test_stress_route.py and confirming that there is no memory leak in zebra after the completion of the test

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211
  • 202305

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

…onic-net#17484)

Fix zebra leaking memory with fib suppress enabled. Porting the fix from
FRRouting/frr#14983

While running test_stress_route.py, systems with lower memory started to throw low memory logs. On further investigation, a memory leak has been found in zebra which was fixed in the FRR community.
@mssonicbld
Copy link
Collaborator Author

Original PR: #17484

@mssonicbld mssonicbld merged commit 8297800 into sonic-net:202305 Dec 15, 2023
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants