diff options
| author | Uday Shankar <[email protected]> | 2023-03-01 00:06:55 +0000 |
|---|---|---|
| committer | Jens Axboe <[email protected]> | 2023-03-03 04:00:20 +0000 |
| commit | 49d24398327e32265eccdeec4baeb5a6a609c0bd (patch) | |
| tree | eac5516659021cb104b90d7b398f18843ff84d8a /tools/perf/scripts/python/flamegraph.py | |
| parent | Merge tag 'nvme-6.3-2022-03-01' of git://git.infradead.org/nvme into for-6.3/... (diff) | |
| download | kernel-49d24398327e32265eccdeec4baeb5a6a609c0bd.tar.gz kernel-49d24398327e32265eccdeec4baeb5a6a609c0bd.zip | |
blk-mq: enforce op-specific segment limits in blk_insert_cloned_request
The block layer might merge together discard requests up until the
max_discard_segments limit is hit, but blk_insert_cloned_request checks
the segment count against max_segments regardless of the req op. This
can result in errors like the following when discards are issued through
a DM device and max_discard_segments exceeds max_segments for the queue
of the chosen underlying device.
blk_insert_cloned_request: over max segments limit. (256 > 129)
Fix this by looking at the req_op and enforcing the appropriate segment
limit - max_discard_segments for REQ_OP_DISCARDs and max_segments for
everything else.
Signed-off-by: Uday Shankar <[email protected]>
Reviewed-by: Keith Busch <[email protected]>
Reviewed-by: Ming Lei <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions
