diff options
author | Christoph Hellwig <hch@lst.de> | 2024-05-23 20:26:13 +0200 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2024-05-28 06:54:36 -0600 |
commit | bafea1c58b24be594d97841ced1b7ae0347bf6e3 (patch) | |
tree | a64b3232ae15d764b608624dd2f17683ce09d8ec /tools/perf/scripts/python/arm-cs-trace-disasm.py | |
parent | 233e27b4d21c3e44eb863f03e566d3a22e81a7ae (diff) |
sd: also set max_user_sectors when setting max_sectors
sd can set a max_sectors value that is lower than the max_hw_sectors
limit based on the block limits VPD page. While this is rather unusual,
it used to work until the max_user_sectors field was split out to cleanly
deal with conflicting hardware and user limits when the hardware limit
changes. Also set max_user_sectors to ensure the limit can properly be
stacked.
Fixes: 4f563a64732d ("block: add a max_user_discard_sectors queue limit")
Reported-by: Mike Snitzer <snitzer@kernel.org>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Acked-by: Mike Snitzer <snitzer@kernel.org>
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
Link: https://lore.kernel.org/r/20240523182618.602003-2-hch@lst.de
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/scripts/python/arm-cs-trace-disasm.py')
0 files changed, 0 insertions, 0 deletions