diff options
| author | Donald Sharp <sharpd@nvidia.com> | 2021-06-24 12:23:33 -0400 |
|---|---|---|
| committer | Donald Sharp <sharpd@nvidia.com> | 2022-02-07 16:10:03 -0500 |
| commit | c6eee91f66956a14d73f6b2f2e43a792c854195a (patch) | |
| tree | b4888f423738147f30ac134df048766fdda1dfb3 /zebra/kernel_socket.c | |
| parent | 16cdf5ddbc5c92f0dc43d9243a60a7258c67e68d (diff) | |
zebra: Fix ships in the night issue
When using wait for install there exists situations where
zebra will issue several route change operations to the kernel
but end up in a state where we shouldn't be at the end
due to extra data being received. Example:
a) zebra receives from bgp a route change, installs sends the
route to the kernel.
b) zebra receives a route deletion from bgp, removes the
struct route entry and then sends to the kernel a deletion.
c) zebra receives an asynchronous notification that (a) succeeded
but we treat this as a new route.
This is the ships in the night problem. In this case if we receive
notification from the kernel about a route that we know nothing
about and we are not in startup and we are doing asic offload
then we can ignore this update.
Ticket: #2563300
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'zebra/kernel_socket.c')
| -rw-r--r-- | zebra/kernel_socket.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/zebra/kernel_socket.c b/zebra/kernel_socket.c index 5ff66f7c63..3c9d203a0b 100644 --- a/zebra/kernel_socket.c +++ b/zebra/kernel_socket.c @@ -1113,7 +1113,7 @@ void rtm_read(struct rt_msghdr *rtm) || rtm->rtm_type == RTM_CHANGE) rib_add(afi, SAFI_UNICAST, VRF_DEFAULT, ZEBRA_ROUTE_KERNEL, 0, zebra_flags, &p, NULL, &nh, 0, RT_TABLE_MAIN, - 0, 0, 0, 0); + 0, 0, 0, 0, false); else rib_delete(afi, SAFI_UNICAST, VRF_DEFAULT, ZEBRA_ROUTE_KERNEL, 0, zebra_flags, &p, NULL, &nh, 0, RT_TABLE_MAIN, 0, |