8000 bgpd: Unset TOVPN_SID_EXPLICIT flag to ensure BGP can release SRv6 SIDs (backport #18969) by mergify[bot] · Pull Request #18973 · FRRouting/frr · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

bgpd: Unset TOVPN_SID_EXPLICIT flag to ensure BGP can release SRv6 SIDs (backport #18969) #18973

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

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link
@mergify mergify bot commented Jun 7, 2025

When a BGP instance is about to be destroyed, we call delete_vrf_tovpn_sid_per_vrf() to release SRv6 SIDs.

This function checks that there are no BGP_VRF_TOVPN_SID_* flags set for this BGP instance. If there are, then it assumes that this BGP instance is still using SRv6, and returns early without releasing the SIDs.

This PR makes sure the BGP_VRF_TOVPN_SID_EXPLICIT flag is unset before calling delete_vrf_tovpn_sid_per_vrf(), so that the delete_vrf_tovpn_sid_per_vrf() can do its job and release the SIDs.


This is an automatic backport of pull request #18969 done by Mergify.

When a BGP instance is about to be destroyed, we call
delete_vrf_tovpn_sid_per_vrf() to release SRv6 SIDs.

This function checks that there are no BGP_VRF_TOVPN_SID_* flags set
for this BGP instance. If there are, then it assumes that this BGP
instance is still using SRv6, and returns early without releasing the
SIDs.

This commit makes sure the BGP_VRF_TOVPN_SID_EXPLICIT flag is unset
before calling delete_vrf_tovpn_sid_per_vrf(), so that the
delete_vrf_tovpn_sid_per_vrf() can do its job and release the SIDs.

Signed-off-by: Carmine Scarpitta <cscarpit@cisco.com>
(cherry picked from commit 0e157ab)

# Conflicts:
#	bgpd/bgpd.c
@mergify mergify bot added the conflicts label Jun 7, 2025
Copy link
Author
mergify bot commented Jun 7, 2025

Cherry-pick of 0e157ab has failed:

On branch mergify/bp/stable/10.2/pr-18969
Your branch is up to date with 'origin/stable/10.2'.

You are currently cherry-picking commit 0e157abc3.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   bgpd/bgpd.c

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@frrbot frrbot bot added the bgp label Jun 7, 2025
@ton31337 ton31337 closed this Jun 7, 2025
@ton31337 ton31337 deleted the mergify/bp/stable/10.2/pr-18969 branch June 7, 2025 10:55
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
0