[202311][FRR]Adding fix for memory leak seen with BGP community

[dgsudharsan]

Porting PR #18272 to 202311.

Why I did it

Porting fix for FRRouting/frr#15459

Adding patch for PR FRRouting/frr#15466

Work item tracking

• Microsoft ADO (number only):

How I did it

Ported the fix FRRouting/frr#15466 to 8.5.1

How to verify it

Running the test_stress_route and ensure no memory leak

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)

[liat-grozovik]

@StormLiangMS please help to review. Tests will be completed very soon and we will to merge once done

[StormLiangMS]

hi @lipxu @jimmyzhai could you help to take review this PR?

[StormLiangMS]

@StormLiangMS please help to review. Tests will be completed very soon and we will to merge once done

Have you verified with 202311 image? PR test has no gating for this one. @liat-grozovik

[lipxu]

LGTM

[dgsudharsan]

@StormLiangMS please help to review. Tests will be completed very soon and we will to merge once done

Have you verified with 202311 image? PR test has no gating for this one. @liat-grozovik

Hi @StormLiangMS . There is no test to verify. 202305 and 202311 have identical FRR. @lipxu verified the fixes in 202305. In my opinion the testing in 202305 is sufficient.

I would also recommend adding a test to sonic-mgmt to cover this scenario.

[StormLiangMS]

LGTM

[StormLiangMS]

oops, 202311 should be Ying to decide to take or not, my bad. @yxieca