[PATCH V2] nvme-fabrics: handle zero MAXCMD without closing the connection
Keith Busch
kbusch at kernel.org
Wed Dec 4 09:20:36 PST 2024
On Tue, Dec 03, 2024 at 01:57:32PM +0100, Maurizio Lombardi wrote:
> The NVMe specification states that MAXCMD is mandatory
> for NVMe-over-Fabrics implementations. However, some NVMe/TCP
> and NVMe/FC arrays from major vendors have buggy firmware
> that reports MAXCMD as zero in the Identify Controller data structure.
>
> Currently, the host implementation returns an error in such cases,
> completely preventing the host from connecting to the target.
>
> Fix the issue by printing a clear warning message about the firmware bug
> and allowing the connection to proceed. It assumes that the
> target supports a MAXCMD value of SQSIZE + 1. If any issues arise,
> the user can manually adjust SQSIZE to mitigate them.
Thanks, applied to nvme-6.13.
More information about the Linux-nvme
mailing list