bird 2.14 segfault

ico ico at petrzalka.net
Thu Feb 8 10:26:07 CET 2024


Hello,

We are running few routers, all Slackware Linux, 64bit. The setup is 
like this: router A is a gateway for whole network, speaking BGP on the 
outside, OSPF on the inside. There are a few routers on the inside, 
let's say B, C, D, ..., all of them are OSPF neighbors to A and each 
other. Routers B, C, etc. are running bird 2.14.

I wanted to upgrade bird on router A from 1.6 to 2.14. As soon as new 
bird started up on A, almost all of B, C, etc. started crashing. Today I 
started to look into this. I found out I messed up the configuration on 
router A, I didn't filter out all routes from BGP and all those prefixes 
(IPv4 only, ~100k) were exported to OSPF. The bird on router A handled 
it quite OK, but routers B, C, etc. segfaulted after few seconds of 
exporting all those prefixes to kernel. And that happened repeatedly 
after bird started again. And again..

In bird's log file I found nothing. In system log were 2 lines for each 
segfault:

[Thu Feb  1 01:51:10 2024] bird[23724]: segfault at 7ffe0e092ff8 ip 
00007f2c4fb219a7 sp 00007ffe0e093000 error 6 in 
libc-2.33.so[7f2c4fabe000+15e000]
[Thu Feb  1 01:51:10 2024] Code: 48 89 d9 49 8b 7f 28 49 8b 5f 30 48 39 
df 73 bf 48 29 fb 4c 39 f3 49 0f 47 de 48 83 fb 14 76 a3 48 89 ce 48 89 
da 48 89 0c 24 <e8> f4 c8 f9 ff 48 8b 0c 24 49 89 47 28 48 01 d9 eb 90 
0f 1f 80 00

I will try again to upgrade router A without all those prefixes exported 
to OSPF, that should work I believe.

I am not good at this, but maybe someone could use this information to 
find a bug somewhere in bird. Maybe I can help and try something with 
the same failing setup?

Thanks

ico


More information about the Bird-users mailing list