[Xorp-hackers] [greearb/xorp.ct] 323cbc: ospf: Deal better with reloading ospf config file...

noreply at github.com noreply at github.com
Fri Apr 22 12:29:50 PDT 2011


Branch: refs/heads/master
Home:   https://github.com/greearb/xorp.ct

Commit: 323cbc6d5fd2e2e3e848fe23c2842d6d76cdb71e
    https://github.com/greearb/xorp.ct/commit/323cbc6d5fd2e2e3e848fe23c2842d6d76cdb71e
Author: Ben Greear <greearb at candelatech.com>
Date:   2011-04-22 (Fri, 22 Apr 2011)

Changed paths:
  M xorp/libfeaclient/ifmgr_atoms.cc
  M xorp/libfeaclient/ifmgr_atoms.hh
  M xorp/ospf/peer.cc
  M xorp/ospf/peer_manager.cc
  M xorp/ospf/xrl_io.cc

Log Message:
-----------
ospf:  Deal better with reloading ospf config files.

Problem is this:  When loading a config file that has a new
interface, the route redistribution messages can come before
the new interface info is pushed.  That could lead to trying
to announce routes when the peer has a zero prefix.

This attempts to fix this by basically removing the assert.
I am hoping that the route redistribution will happen properly
when the peer comes up, but I'm not certain that is the case.
So, maybe more fixes coming..but at least we don't crash now.

Core was generated by `xorp_ospfv2'.
Program terminated with signal 6, Aborted.
(gdb) bt
    at libxorp/xlog.c:480
    a3=0xffffffffffffffff <Address 0xffffffffffffffff out of bounds>, a4=140733526888592) at ./libxorp/callback_nodebug.hh:8966

Signed-off-by: Ben Greear <greearb at candelatech.com>




More information about the Xorp-hackers mailing list