]> git.puffer.fish Git - mirror/frr.git/commit
When internal operations are performed (e.g., best-path selection, next-hop
authorDonald Sharp <sharpd@cumulusnetworks.com>
Wed, 20 May 2015 01:03:50 +0000 (18:03 -0700)
committerDonald Sharp <sharpd@cumulusnetworks.com>
Wed, 20 May 2015 01:03:50 +0000 (18:03 -0700)
commit75aead62b763031dae21ceda615fec5a148ae715
tree6cd6781b3fb7004c53aa0f7ed736e2908a48a0c9
parent97dba7b704f18c66f16e9330821514a79f982fdb
When internal operations are performed (e.g., best-path selection, next-hop
change processing etc.) that refer to the BGP instance, the correct BGP
instance must be referenced and not the default BGP instance. The default
BGP instance is the first instance on the instance list. In a scenario
where one BGP instance is deleted (through operator action such as a
"no router bgp" command) and another instance exists or is created, there
may still be events in-flight that need to be processed against the
deleted instance. Trying to process these against the default instance
is erroneous. The calls to bgp_get_default() must be limited to the user
interface (vtysh) context.

Signed-off-by: Vivek Venkatraman <vivek@cumulusnetworks.com>
bgpd/bgp_attr.c
bgpd/bgp_fsm.c
bgpd/bgp_nexthop.h
bgpd/bgp_nht.c
bgpd/bgp_nht.h
bgpd/bgp_route.c