Whamcloud - gitweb
LU-15047 gss: gss integrity check with multi-rail
authorSebastien Buisson <sbuisson@ddn.com>
Mon, 18 Oct 2021 11:26:40 +0000 (13:26 +0200)
committerAndreas Dilger <adilger@whamcloud.com>
Sat, 17 Jun 2023 05:36:28 +0000 (05:36 +0000)
commitc84861f7ffe45591d86bb0178b44a9f1c9372b8c
treed1524d3cd949347d0ecd287d78b33887d4730d1e
parentd7838d329316f641e3e0bb401c8415c605caac26
LU-15047 gss: gss integrity check with multi-rail

With multi-rail, a primary NID is used as node identifier, but LNet
decides which NID is actually used for sending/receiving data, on a
per request basis.
For the integrity check mechanism implemented as part of GSS, the
primary NID must be used in order to compute HMAC with the correct
key, independently of the actual NID for the current request.

Lustre-change: https://review.whamcloud.com/45277
Lustre-commit: c8301a65c5672a1d081669343466746df983eabc

Signed-off-by: Sebastien Buisson <sbuisson@ddn.com>
Change-Id: I2bf3974d3aa0e8365a9413dca56c69ee3734c12b
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Reviewed-on: https://review.whamcloud.com/c/ex/lustre-release/+/51274
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Andreas Dilger <adilger@whamcloud.com>
lustre/ptlrpc/gss/gss_keyring.c
lustre/ptlrpc/gss/gss_svc_upcall.c