OSDN Git Service

nvme-fc: print proper nvme-fc devloss_tmo value
authorMartin George <marting@netapp.com>
Tue, 12 May 2020 16:47:04 +0000 (22:17 +0530)
committerChristoph Hellwig <hch@lst.de>
Wed, 27 May 2020 05:12:37 +0000 (07:12 +0200)
commit614fc1c0d980423a131bfb5c93d8d53e5272f587
tree9ccf1fd73caa795d9fb8b1b09b1074d82fd4a946
parent9c9e76d5792b121f10c3b8ddbb639617e49197f7
nvme-fc: print proper nvme-fc devloss_tmo value

The nvme-fc devloss_tmo is computed as the min of either the
ctrl_loss_tmo (max_retries * reconnect_delay) or the remote port's
devloss_tmo. But what gets printed as the nvme-fc devloss_tmo in
nvme_fc_reconnect_or_delete() is always the remote port's devloss_tmo
value. So correct this by printing the min value instead.

Signed-off-by: Martin George <marting@netapp.com>
Reviewed-by: James Smart <james.smart@broadcom.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
drivers/nvme/host/fc.c