-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Bgpd crash on shutdown when have VRFs and leaked routes #2184
Comments
I think there's a typo there, not sure what is being referred to. |
run the topotest and you can examine the log and core and form your own
opinions.
…On 5/8/2018 3:19 PM, Quentin Young wrote:
Examination of the debug outputs show that appear goes down in one
thread...
I think there's a typo there, not sure what is being referred to.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2184 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGRWyLoI7kaqg52XgtV4vqW_rPg20BMjks5twe_XgaJpZM4T14KN>.
|
Oh, you must have been trying to say "a peer" and not "appear". Thanks for the clarification. |
race condition avoided, but still have crash, see #2198 -- which is a band aid around a double free. |
Asan shows the issue as being on vrf leaked routes:
|
Current version of asan errors: 0x60e00004ead0 is located 80 bytes inside of 160-byte region [0x60e00004ea80,0x60e00004eb20) previously allocated by thread T0 here: SUMMARY: AddressSanitizer: heap-use-after-free ../lib/table.h:238 in route_unlock_node |
#2335 might fix this |
Probably fixed as Donald says. If not, let's reopen on demand. |
As seen in https://github.com/FRRouting/topotests/tree/master/bgp_l3vpn_to_bgp_vrf
Examination of the debug outputs show that a peer goes down in one thread while shutdown is taking place in the other thread. This results in the crash. Experimentation confirms this...
The text was updated successfully, but these errors were encountered: