Ming LeiandGreg Kroah-Hartman 9ebc344ce5 nvme: fix handling single range discard request ...

[ Upstream commit 37f0dc2ec7 ]

When investigating one customer report on warning in nvme_setup_discard,
we observed the controller(nvme/tcp) actually exposes
queue_max_discard_segments(req->q) == 1.

Obviously the current code can't handle this situation, since contiguity
merge like normal RW request is taken.

Fix the issue by building range from request sector/nr_sectors directly.

Fixes: b35ba01ea6 ("nvme: support ranged discard requests")
Signed-off-by: Ming Lei <ming.lei@redhat.com>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Sasha Levin <sashal@kernel.org>

2023-03-22 13:29:59 +01:00

..

core.c

nvme: fix handling single range discard request

2023-03-22 13:29:59 +01:00

fabrics.c

…

fabrics.h

…

fault_inject.c

…

fc.c

…

fc.h

…

hwmon.c

nvme-hwmon: kmalloc the NVME SMART log buffer

2022-10-30 09:41:17 +01:00

Kconfig

…

lightnvm.c

nvme: split nvme_alloc_request()

2022-06-29 08:59:49 +02:00

Makefile

…

multipath.c

…

nvme.h

nvme: fix multipath crash caused by flush request when blktrace is enabled

2023-01-14 10:16:49 +01:00

pci.c

nvme-pci: fix timeout request state check

2023-02-01 08:23:15 +01:00

rdma.c

nvme: fix regression when disconnect a recovering ctrl

2022-07-21 21:20:15 +02:00

tcp.c

nvme-tcp: fix regression that causes sporadic requests to time out

2022-09-15 11:32:06 +02:00

trace.c

…

trace.h

nvme: use command_id instead of req->tag in trace_nvme_complete_rq()

2022-08-21 15:16:03 +02:00

zns.c

…