Nest: Fix several issues with pflags
There were some confusion about validity and usage of pflags, which caused incorrect usage after some flags from (now removed) protocol- specific area were moved to pflags. We state that pflags: - Are secondary data used by protocol-specific hooks - Can be changed on an existing route (in contrast to copy-on-write for primary data) - Are irrelevant for propagation (not propagated when changed) - Are specific to a routing table (not propagated by pipe) The patch did these fixes: - Do not compare pflags in rte_same(), as they may keep cached values like BGP_REF_STALE, causing spurious propagation. - Initialize pflags to zero in rte_get_temp(), avoid initialization in protocol code, fixing at least two forgotten initializations (krt and one case in babel). - Improve documentation about pflags
Showing
- nest/rt-dev.c 0 additions, 1 deletionnest/rt-dev.c
- nest/rt-table.c 12 additions, 9 deletionsnest/rt-table.c
- proto/babel/babel.c 0 additions, 1 deletionproto/babel/babel.c
- proto/bgp/packets.c 0 additions, 1 deletionproto/bgp/packets.c
- proto/perf/perf.c 0 additions, 1 deletionproto/perf/perf.c
- proto/pipe/pipe.c 0 additions, 7 deletionsproto/pipe/pipe.c
- proto/rpki/rpki.c 0 additions, 2 deletionsproto/rpki/rpki.c
- proto/static/static.c 0 additions, 1 deletionproto/static/static.c
Loading