NVMe SGL Data Length Error

[keith.busch@linux.intel.com (Keith Busch)]

On Tue, Jul 10, 2018@05:28:25PM +0000, Andrew Maier wrote:
> Hi all,
> 
> I've run into an issue with NVMe SGLs lately with our controller when given multiple SGL segments in a single command from the driver (i.e., more than 256 SGL entries in a single nvme read/write command); where there are not enough SGL Data Block descriptors for the transfer.  The first segment properly links to, in my case, a Last Segment Descriptor, however at the end of the second segment there are not enough Data Block descriptors for the full transfer (it is usually missing space for 4096 or 8192 bytes) which I've verified manually using a PCIe analyzer.  This forces our NVMe Controller to fail and return the SGL Data Length Invalid (0xF) status code.
> 
> Repro Steps:
> 1. Set the sgl_threshold to 4096
> 2. Run a 4MB nvme read transfer (i.e., nvme read <sgl_nvme_dev> -s 0 -c 8191 -z 4194304 -t)
> 3. Repeat step 2 until the memory is split into multiple SGL segments or try a larger transfer.
> 
> Does anyone know of a patch for this issue?

Probably not the fix you were hoping for, but the following commit
will limit the number of SGL entries to 127 for PCI devices, so it'd
always only have 1 segment descriptor.

  https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=943e942e6266f22babee5efeb00f8f672fbff5bd