<html><head></head><body><div dir="auto">Hello, Radu! <br><br>We apparently missed this case in our test scenarios, so we'll add one and check if it reproduces. We'll ask for more info if we need it.<br><br>Congratulations to the first BIRD 3 bugreport and thanks for it!<br><br>Maria<br></div><br><br><div class="gmail_quote"><div dir="auto">On 18 December 2024 14:27:44 CET, Radu Anghel via Bird-users <bird-users@network.cz> wrote:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail"><div dir="auto">Hi,<br><br>Using a slightly modified version of the config from the 2.15.1 (just some {} inside case structures), but probably unrelated.<br><br>If bird gets killed/not shut down properly and routes remain in the kernel then bird 3.0.0 is unable to restart and just segfaults when trying to refresh kernel routes.<br><br>I can reproduce it by just kill -9 bird && restarting bird.<br><br>daemon.debug bird: KERNEL6.ipv6: route refresh begin: rr 1 set 1 valid 0 pruning 0 pruned 0<br><br>kern.info kernel: [75645.964935] bird[4162]: segfault at 0 ip 000000000045d47b sp 00007ffcb9f9f2c0 error 4 in bird[403000+a8000] likely on CPU 1 (core 0, socket 1)<br><br>kern.info kernel: [75645.970115] Code: 5d 41 5c 41 5d 41 5e 41 5f c3 55 53 48 89 fb 48 83 ec 38 80 bb 79 02 00 00 04 48 8b 7f 30 75 46 48 89 d5 31 d2 e8 63 a4 ff ff <83> 38 00 49 89 c0 75 07 31 c0 e9 9d 00 00 00 48 8b 40 10 48 8d 7b<br><br>The kernel protocol config is:<br><br>protocol kernel KERNEL6 {<br> debug { events, states };<br> scan time 3600;<br><br> merge paths on;<br><br> metric 0;<br> ipv6 {<br> import filter KERNEL_IN;<br> export filter KERNEL_OUT;<br> };<br>}<br><br>Cheers,<br><br>R<br><br></div></pre></blockquote></div><div dir="auto"><div class='k9mail-signature'>-- <br>Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.</div></div></body></html>