From eee4358d9d467d22cdde3ad63e4fe4f9cebeebcf Mon Sep 17 00:00:00 2001 From: Amir Shehata Date: Wed, 22 Apr 2020 17:54:34 -0700 Subject: [PATCH] LU-13472 lnet: set route aliveness properly In the case when the discover is toggled from on to off, the route aliveness might become stale due to not updating the route->lr_alive variable correctly. It will get updated once the gateway is pinged. However, there is a period of max alive_router_check_interval where the route can be down. Test-Parameters: trivial testlist=sanity-lnet Signed-off-by: Amir Shehata Change-Id: Ic1754d6e7ddc9398efc7a64f823a70e5546e9ca6 Reviewed-on: https://review.whamcloud.com/38323 Tested-by: jenkins Reviewed-by: Chris Horn Reviewed-by: Serguei Smirnov Tested-by: Maloo Reviewed-by: Oleg Drokin --- lnet/lnet/router.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/lnet/lnet/router.c b/lnet/lnet/router.c index 3e90c30..3fb67db 100644 --- a/lnet/lnet/router.c +++ b/lnet/lnet/router.c @@ -526,8 +526,10 @@ lnet_router_discovery_complete(struct lnet_peer *lp) * the gateway we assume this is intentional and we mark the * gateway as multi-hop */ - list_for_each_entry(route, &lp->lp_routes, lr_gwlist) + list_for_each_entry(route, &lp->lp_routes, lr_gwlist) { + lnet_set_route_aliveness(route, true); lnet_set_route_hop_type(lp, route); + } return; } -- 1.8.3.1