bird-1.5.0 ipv4 segfaults on configure - is it safe to change bgp protocol names runtime?

[Bartosz Radwan]

On 18.03.2016 10:07, Jan Matejka wrote:
> Can you please send in a reduced config set that still causes this bug?
> I'd like to reproduce it locally and fix it thereafter.
>
> Thanks a lot.
Minimal config causing the errors:

protocol direct {

         interface "br0.*", "br1", "br1.*";
         debug all;
}
protocol kernel {
         learn;
         persist;
         scan time 1;
         export all;
}
protocol device {
         scan time 1;
}
protocol bgp one {

     router id 10.13.0.31;
     debug all;
     next hop self;
     direct;
     import none;
     export filter { if net = 10.10.10.0/24 then {accept;  accept; } 
reject; };
     local 10.13.0.1 as 65532;
     neighbor 10.13.0.2 as 65531;
     check link 1;
}


Testing this one ive got another segfault, seems quite random…:

bird: Reconfiguring
bird: direct1: Reconfigured
bird: Removing protocol one_SOME_LONGER_NAME_2_3
bird: one_SOME_LONGER_NAME_2_3: Shutting down
bird: one_SOME_LONGER_NAME_2_3: Shutdown requested
bird: one_SOME_LONGER_NAME_2_3: State changed to stop
bird: Adding protocol one
bird: one: Initializing
bird: one: Starting
bird: one: State changed to start
bird: one_SOME_LONGER_NAME_2_3: Down
bird: one_SOME_LONGER_NAME_2_3: State changed to down
bird: Reconfigured

Program received signal SIGSEGV, Segmentation fault.
0x000000000044574f in pool_free (P=<optimized out>) at resource.c:81
81            r->class->free(r);
(gdb) bt
#0  0x000000000044574f in pool_free (P=<optimized out>) at resource.c:81
#1  0x00000000004457c3 in rfree (res=0x6807c0) at resource.c:165
#2  0x000000000043a89d in config_free (c=<optimized out>) at conf.c:174
#3  0x000000000043a8d3 in config_do_commit (c=c at entry=0x68db10, 
type=type at entry=1) at conf.c:230
#4  0x000000000043ac54 in config_commit (c=0x68db10, type=type at entry=1, 
timeout=timeout at entry=0) at conf.c:348
#5  0x0000000000441997 in cmd_reconfig (name=<optimized out>, 
type=type at entry=1, timeout=0) at main.c:312
#6  0x0000000000437245 in cf_parse () at cf-parse.y:917
#7  0x000000000043a87f in cli_parse (c=c at entry=0x7fffffffdb20) at conf.c:159
#8  0x000000000040de34 in cli_command (c=c at entry=0x66eb30) at 
../../nest/cli.c:270
#9  0x000000000040e00c in cli_event (data=0x66eb30) at ../../nest/cli.c:297
#10 0x000000000043b76e in ev_run (e=0x66db10) at event.c:85
#11 ev_run_list (l=0x66b2e0 <global_event_list>) at event.c:142
#12 0x000000000043de3c in io_loop () at io.c:2061
#13 0x00000000004031d3 in main (argc=<optimized out>, argv=<optimized 
out>) at main.c:833

I'm not sure if it's bird error at all. If you do not reproduce this 
errors it will be hint for me and i'll start investigtion in linked libs 
etc.

Tkanks a lot.

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Z poważaniem
Bartosz Radwan