RDMA/rtrs: Do not reset hb_missed_max after re-connection
[ Upstream commit 64bce1ee978491a779eb31098b21c57d4e431d6a ] When re-connecting, it resets hb_missed_max to 0. Before the first re-connecting, client will trigger re-connection when it gets hb-ack more than 5 times. But after the first re-connecting, clients will do re-connection whenever it does not get hb-ack because hb_missed_max is 0. There is no need to reset hb_missed_max when re-connecting. hb_missed_max should be kept until closing the session. Fixes: c0894b3ea69d3 ("RDMA/rtrs: core: lib functions shared between client and server modules") Link: https://lore.kernel.org/r/20210528113018.52290-16-jinpu.wang@ionos.com Signed-off-by: Gioh Kim <gi-oh.kim@ionos.com> Signed-off-by: Jack Wang <jinpu.wang@ionos.com> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
parent
bd4df557ae
commit
f03d4c1296
@ -373,7 +373,6 @@ void rtrs_stop_hb(struct rtrs_sess *sess)
|
||||
{
|
||||
cancel_delayed_work_sync(&sess->hb_dwork);
|
||||
sess->hb_missed_cnt = 0;
|
||||
sess->hb_missed_max = 0;
|
||||
}
|
||||
EXPORT_SYMBOL_GPL(rtrs_stop_hb);
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user