diff options
| author | Ming Lei <[email protected]> | 2023-03-04 07:13:45 +0800 |
|---|---|---|
| committer | Christoph Hellwig <[email protected]> | 2023-03-15 14:58:51 +0100 |
| commit | 37f0dc2ec78af0c3f35dd05578763de059f6fe77 (patch) | |
| tree | 62824802413e8c4bf0ac1330995636c2603c9e49 /drivers/usb/cdns3/cdns3-trace.c | |
| parent | 54686b611eb054a5c84976e6f6e03788fa8e6a38 (diff) | |
nvme: fix handling single range discard request
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: b35ba01ea697 ("nvme: support ranged discard requests")
Signed-off-by: Ming Lei <[email protected]>
Reviewed-by: Chaitanya Kulkarni <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Diffstat (limited to 'drivers/usb/cdns3/cdns3-trace.c')
0 files changed, 0 insertions, 0 deletions