Christoph Hellwig 33b93727ce nvme: fix setting the queue depth in nvme_alloc_io_tag_set ... While the CAP.MQES field in NVMe is a 0s based filed with a natural one off, we also need to account for the queue wrap condition and fix undo the one off again in nvme_alloc_io_tag_set. This was never properly done by the fabrics drivers, but they don't seem to care because there is no actual physical queue that can wrap around, but it became a problem when converting over the PCIe driver. Also add back the BLK_MQ_MAX_DEPTH check that was lost in the same commit. Fixes: 0da7feaa59 ("nvme-pci: use the tagset alloc/free helpers") Reported-by: Hugh Dickins <hughd@google.com> Signed-off-by: Christoph Hellwig <hch@lst.de> Tested-by: Hugh Dickins <hughd@google.com> Link: https://lore.kernel.org/r/20221225103234.226794-2-hch@lst.de Signed-off-by: Jens Axboe <axboe@kernel.dk>		2022-12-26 12:10:51 -07:00
..
common	treewide: use get_random_u32() when possible	2022-10-11 17:42:58 -06:00
host	nvme: fix setting the queue depth in nvme_alloc_io_tag_set	2022-12-26 12:10:51 -07:00
target	for-6.2/block-2022-12-08	2022-12-13 10:43:59 -08:00
Kconfig	nvme: implement In-Band authentication	2022-08-02 17:14:49 -06:00
Makefile	nvme: implement In-Band authentication	2022-08-02 17:14:49 -06:00