On Tue, 14 Jul 2020 14:14:12 -0700, James Smart wrote:
> Nvme-fc allows the driver to specify a default devloss_tmo value when
> registering the remote port. The lpfc driver is currently not doing so
> although it is implementing a driver internal node loss value of 30s
> which also is used on the scsi fc remote port. As no devloss_tmo is set,
> the nvme-fc transport defaults to 60s. So there's competing timers.
>
> Additionally, due to the competing timers, its possible the nvme rport
> is removed but the scsi rport remains. Its possible that the scsi fc
> rport, which was registered for the nvme port even if it doesn't utilize
> the scsi protocol, had been tuned to not match either the 60s (nvme-fc
> default) or 30s (lldd default), it gets out of whack. The lldd will
> defer to the scsi fc rport as long as the scsi fc rport has not had its
> devloss_tmo expire.
>
> [...]
Applied to 5.9/scsi-queue, thanks!
[1/1] scsi: lpfc: NVMe remote port devloss_tmo from lldd
https://git.kernel.org/mkp/scsi/c/1f5468231476
--
Martin K. Petersen Oracle Linux Engineering
