From: Gabriel Goller <g.goller@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH frr v2 0/3] Backport FRR EVPN local RT2 leaking fixes
Date: Fri, 15 May 2026 14:03:44 +0200 [thread overview]
Message-ID: <20260515120351.395649-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. This PR also needs the #21511 [3] PR as a prerequisite.
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
[3]: https://github.com/FRRouting/frr/pull/21511
Changelog:
v2:
* instead of absorbing the fix into the commits of #20005, cherry pick the
fixing commit from #21511
frr:
Gabriel Goller (3):
frr: backport "bgpd: fix valgrind memory leaks on daemon shutdown"
(#21511)
frr: backport the "Memory leak problems." (#21844) upstream PR
bump to version 10.6.1-1+pve2
debian/changelog | 6 +
debian/patches/series | 21 +
...rind-memory-leaks-on-daemon-shutdown.patch | 89 ++
...nup-complaint-about-unneeded-destroy.patch | 77 ++
...p-termination-cleanup-of-memory-leak.patch | 47 +
.../0008-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 | 608 ++++++++++++
...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 ++
.../0018-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 ++++
.../0022-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 ++++++++++
23 files changed, 3799 insertions(+)
create mode 100644 debian/patches/upstream/0005-bgpd-fix-valgrind-memory-leaks-on-daemon-shutdown.patch
create mode 100644 debian/patches/upstream/0006-pim6d-cleanup-complaint-about-unneeded-destroy.patch
create mode 100644 debian/patches/upstream/0007-lib-nexthop-group-termination-cleanup-of-memory-leak.patch
create mode 100644 debian/patches/upstream/0008-lib-ferr-memory-leaked.patch
create mode 100644 debian/patches/upstream/0009-zebra-fpm_listener-has-signal-handlers-now.patch
create mode 100644 debian/patches/upstream/0010-tests-Remove-log-file-isisd.log-from-all-isis-tests.patch
create mode 100644 debian/patches/upstream/0011-tests-Tell-fpm_listener-to-shutdown.patch
create mode 100644 debian/patches/upstream/0012-isisd-Clean-up-and-memory-leaks-in-isis.patch
create mode 100644 debian/patches/upstream/0013-bgpd-Cleanup-memory-leaks-on-shutdown.patch
create mode 100644 debian/patches/upstream/0014-ripd-Cleanup-memory-leaks-on-shutdown.patch
create mode 100644 debian/patches/upstream/0015-pbrd-termination-cleanup-of-memory-leaks.patch
create mode 100644 debian/patches/upstream/0016-nhrpd-Cleanup-nhrpd-termination-memory-leaks.patch
create mode 100644 debian/patches/upstream/0017-sharpd-memory-leaks-on-shutdown-cleanup.patch
create mode 100644 debian/patches/upstream/0018-ospfd-memory-leaks-on-shutdown.patch
create mode 100644 debian/patches/upstream/0019-lib-Cleanup-memory-leaks-in-shutdown-in-affinitymaps.patch
create mode 100644 debian/patches/upstream/0020-zebra-cleanup-memory-leaks-on-shutdown.patch
create mode 100644 debian/patches/upstream/0021-ldpd-Fixup-memory-leaks-on-shutdown.patch
create mode 100644 debian/patches/upstream/0022-Cleanup-snmp-memory-leaks.patch
create mode 100644 debian/patches/upstream/0023-pimd-cleanup-of-leaked-memory-on-shutdown.patch
create mode 100644 debian/patches/upstream/0024-tests-make-the-topotest-fail-if-a-memory-leak-is-det.patch
create mode 100644 debian/patches/upstream/0025-Use-hash_clean_and_free-remove-hash_free.patch
Summary over all repositories:
23 files changed, 3799 insertions(+), 0 deletions(-)
--
Generated by murpp 0.11.0
next reply other threads:[~2026-05-15 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 12:03 Gabriel Goller [this message]
2026-05-15 12:03 ` [PATCH frr v2 1/3] frr: backport "bgpd: fix valgrind memory leaks on daemon shutdown" (#21511) Gabriel Goller
2026-05-15 12:03 ` [PATCH frr v2 2/3] frr: backport the "Memory leak problems." (#21844) upstream PR Gabriel Goller
2026-05-15 12:03 ` [PATCH frr v2 3/3] bump to version 10.6.1-1+pve2 Gabriel Goller
2026-05-16 23:59 ` [PATCH frr v2 0/3] Backport FRR EVPN local RT2 leaking fixes Thomas Lamprecht
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=20260515120351.395649-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.