Re: [PATCH frr v2 0/3] Backport FRR EVPN local RT2 leaking fixes

[Thomas Lamprecht <t.lamprecht@proxmox.com>]

On Fri, 15 May 2026 14:03:44 +0200, Gabriel Goller wrote:
> 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]).
> 
> [...]

Tested thise one with 500 VXLAN+bridge churn cycles on a host with the EVPN
address-family active (no leaks, no asserts, +12 KB bgpd RSS) and a `no router
bgp` with an active VNI to exercise the new cleanup path (runs clean). The 21
commits across both upstream PRs (#21511 and #21844) were also checked against
upstream and are logically equivalent; deviations are limited to a few hunks
that account for backport-target context that doesn't exist in 10.6.1 yet, so:

Applied, thanks!

btw. I resolved the merge conflict with the other series, but it isn't perfect
git history wise - but we probably won't have to bisect these two commits on
the packaging level, or rather, one can relatively easy work around doing so.

[1/3] frr: backport "bgpd: fix valgrind memory leaks on daemon shutdown" (#21511)
      commit: 6ddac172c96f3bad0f90f5d61876e98344c33c0c
[2/3] frr: backport the "Memory leak problems." (#21844) upstream PR
      commit: 4e14853e8f9d59d47b5f35792ce6efe601601d5f
[3/3] bump to version 10.6.1-1+pve2
      commit: 9f188e1b4459edfd6174aa1ad48ee4ab6bde7749