From: Gabriel Goller <g.goller@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH frr 0/2] Backport FRR EVPN local RT2 leaking fixes
Date: Fri, 15 May 2026 11:14:28 +0200 [thread overview]
Message-ID: <20260515091440.134414-1-g.goller@proxmox.com> (raw)
Since packaging 10.6.1, we also pull in the EVPN local RT2 leaking patches
(which are applied on upstream master).
The RT2 route leaking PR seems to have some race-condition-related problems,
namely a crash at bgp router shutdown and one case in which the rt2 route is not
leaked (see the last comment at #20005 [1]).
I was not able to reproduce both of these issues, but they seem to be fixed in
the upstream CI with #21844 [2], which solves multiple memory-related issues in
multiple dameons.
In order to be on the safe side, pull these in.
The backporting was a bit of a struggle, because frr-10.6.1..master now also
contains the new BGP-LS address-family (again, after it was reverted out of 10.5
:)) which changes a lot of core bgp structures.
[1]: https://github.com/FRRouting/frr/pull/20005
[2]: https://github.com/FRRouting/frr/pull/21844
frr:
Gabriel Goller (2):
frr: backport the "Memory leak problems." (#21844) upstream PR
bump to version 10.6.1-1+pve2
debian/changelog | 6 +
debian/patches/series | 20 +
...nup-complaint-about-unneeded-destroy.patch | 77 ++
...p-termination-cleanup-of-memory-leak.patch | 47 +
.../0007-lib-ferr-memory-leaked.patch | 48 +
...fpm_listener-has-signal-handlers-now.patch | 55 ++
...g-file-isisd.log-from-all-isis-tests.patch | 883 ++++++++++++++++++
...-tests-Tell-fpm_listener-to-shutdown.patch | 52 ++
...sd-Clean-up-and-memory-leaks-in-isis.patch | 324 +++++++
...gpd-Cleanup-memory-leaks-on-shutdown.patch | 618 ++++++++++++
...ipd-Cleanup-memory-leaks-on-shutdown.patch | 58 ++
...-termination-cleanup-of-memory-leaks.patch | 126 +++
...eanup-nhrpd-termination-memory-leaks.patch | 105 +++
...rpd-memory-leaks-on-shutdown-cleanup.patch | 80 ++
.../0017-ospfd-memory-leaks-on-shutdown.patch | 38 +
...ry-leaks-in-shutdown-in-affinitymaps.patch | 32 +
...bra-cleanup-memory-leaks-on-shutdown.patch | 175 ++++
...-ldpd-Fixup-memory-leaks-on-shutdown.patch | 207 ++++
.../0021-Cleanup-snmp-memory-leaks.patch | 121 +++
...cleanup-of-leaked-memory-on-shutdown.patch | 41 +
...opotest-fail-if-a-memory-leak-is-det.patch | 126 +++
...hash_clean_and_free-remove-hash_free.patch | 480 ++++++++++
22 files changed, 3719 insertions(+)
create mode 100644 debian/patches/upstream/0005-pim6d-cleanup-complaint-about-unneeded-destroy.patch
create mode 100644 debian/patches/upstream/0006-lib-nexthop-group-termination-cleanup-of-memory-leak.patch
create mode 100644 debian/patches/upstream/0007-lib-ferr-memory-leaked.patch
create mode 100644 debian/patches/upstream/0008-zebra-fpm_listener-has-signal-handlers-now.patch
create mode 100644 debian/patches/upstream/0009-tests-Remove-log-file-isisd.log-from-all-isis-tests.patch
create mode 100644 debian/patches/upstream/0010-tests-Tell-fpm_listener-to-shutdown.patch
create mode 100644 debian/patches/upstream/0011-isisd-Clean-up-and-memory-leaks-in-isis.patch
create mode 100644 debian/patches/upstream/0012-bgpd-Cleanup-memory-leaks-on-shutdown.patch
create mode 100644 debian/patches/upstream/0013-ripd-Cleanup-memory-leaks-on-shutdown.patch
create mode 100644 debian/patches/upstream/0014-pbrd-termination-cleanup-of-memory-leaks.patch
create mode 100644 debian/patches/upstream/0015-nhrpd-Cleanup-nhrpd-termination-memory-leaks.patch
create mode 100644 debian/patches/upstream/0016-sharpd-memory-leaks-on-shutdown-cleanup.patch
create mode 100644 debian/patches/upstream/0017-ospfd-memory-leaks-on-shutdown.patch
create mode 100644 debian/patches/upstream/0018-lib-Cleanup-memory-leaks-in-shutdown-in-affinitymaps.patch
create mode 100644 debian/patches/upstream/0019-zebra-cleanup-memory-leaks-on-shutdown.patch
create mode 100644 debian/patches/upstream/0020-ldpd-Fixup-memory-leaks-on-shutdown.patch
create mode 100644 debian/patches/upstream/0021-Cleanup-snmp-memory-leaks.patch
create mode 100644 debian/patches/upstream/0022-pimd-cleanup-of-leaked-memory-on-shutdown.patch
create mode 100644 debian/patches/upstream/0023-tests-make-the-topotest-fail-if-a-memory-leak-is-det.patch
create mode 100644 debian/patches/upstream/0024-Use-hash_clean_and_free-remove-hash_free.patch
Summary over all repositories:
22 files changed, 3719 insertions(+), 0 deletions(-)
--
Generated by murpp 0.11.0
next reply other threads:[~2026-05-15 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 9:14 Gabriel Goller [this message]
2026-05-15 9:14 ` [PATCH frr 1/2] frr: backport the "Memory leak problems." (#21844) upstream PR Gabriel Goller
2026-05-15 9:14 ` [PATCH frr 2/2] bump to version 10.6.1-1+pve2 Gabriel Goller
2026-05-15 12:06 ` [PATCH frr 0/2] Backport FRR EVPN local RT2 leaking fixes Gabriel Goller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260515091440.134414-1-g.goller@proxmox.com \
--to=g.goller@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox