Whamcloud - gitweb
LU-13781 lnet: Local NI must be on same net as next-hop
authorChris Horn <chris.horn@hpe.com>
Sun, 12 Jul 2020 15:47:55 +0000 (10:47 -0500)
committerAndreas Dilger <adilger@whamcloud.com>
Fri, 9 Sep 2022 01:38:40 +0000 (01:38 +0000)
commit1a667fec1ee1397be1b66ddcc3d5069d7883e7e7
treee2b43e2a78faba3f0149cfc0a789fb92ee5e2c29
parente21b40d4b85fe9a0bd4b986f909dfdc3129102cc
LU-13781 lnet: Local NI must be on same net as next-hop

When sending to a remote peer we need to restrict our selection of a
local NI to those on the same peer net as the next-hop.

The code currently selects a local NI on the peer net specified by the
lr_lnet field of the lnet_route returned by lnet_find_route_locked().
However, lnet_find_route_locked() may select a next-hop peer NI on any
local peer net - not just lr_lnet.

A redundant assignment to sd->sd_msg->msg_src_nid_param is also
removed. That variable is always set appropriately in
lnet_select_pathway().

Lustre-change: https://review.whamcloud.com/39352
Lustre-commit: 031c087f3847777c0099cbfae13f0b6fee54452b

Test-Parameters: trivial
HPE-bug-id: LUS-9095
Signed-off-by: Chris Horn <chris.horn@hpe.com>
Change-Id: If1bec26d6646b9e66b99656d7db2dc538d631a34
Reviewed-on: https://review.whamcloud.com/48381
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Frank Sehr <fsehr@whamcloud.com>
Reviewed-by: Alexandre Ioffe <aioffe@ddn.com>
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
lnet/lnet/lib-move.c