Alistair Francis a8576f1e80 nvme: Use non zero KATO for persistent discovery connections ...

[ Upstream commit 2e48265501 ]

The NVMe Base Specification 2.1 states that:

"""
A host requests an explicit persistent connection ... by specifying a
non-zero Keep Alive Timer value in the Connect command.
"""

As such if we are starting a persistent connection to a discovery
controller and the KATO is currently 0 we need to update KATO to a non
zero value to avoid continuous timeouts on the target.

Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Keith Busch <kbusch@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>

2025-11-13 15:34:07 -05:00

..

common

…

host

nvme: Use non zero KATO for persistent discovery connections

2025-11-13 15:34:07 -05:00

target

nvmet-fc: avoid scheduling association deletion twice

2025-11-13 15:34:06 -05:00

Kconfig

…

Makefile

…