aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_jpeg.c
diff options
context:
space:
mode:
authorZhang Yi <[email protected]>2025-09-10 11:11:07 +0000
committerJens Axboe <[email protected]>2025-09-17 14:20:49 +0000
commit027a7a9c07d0d759ab496a7509990aa33a4b689c (patch)
treedadc26beb3faa0befba4e2b4e08e3e395e2fe7f9 /drivers/gpu/drm/amd/amdgpu/amdgpu_jpeg.c
parentMerge tag 'md-6.17-20250917' of https://git.kernel.org/pub/scm/linux/kernel/g... (diff)
downloadkernel-027a7a9c07d0d759ab496a7509990aa33a4b689c.tar.gz
kernel-027a7a9c07d0d759ab496a7509990aa33a4b689c.zip
drbd: init queue_limits->max_hw_wzeroes_unmap_sectors parameter
The parameter max_hw_wzeroes_unmap_sectors in queue_limits should be equal to max_write_zeroes_sectors if it is set to a non-zero value. However, when the backend bdev is specified, this parameter is initialized to UINT_MAX during the call to blk_set_stacking_limits(), while only max_write_zeroes_sectors is adjusted. Therefore, this discrepancy triggers a value check failure in blk_validate_limits(). Since the drvd driver doesn't yet support unmap write zeroes, so fix this failure by explicitly setting max_hw_wzeroes_unmap_sectors to zero. Fixes: 0c40d7cb5ef3 ("block: introduce max_{hw|user}_wzeroes_unmap_sectors to queue limits") Signed-off-by: Zhang Yi <[email protected]> Reviewed-by: Martin K. Petersen <[email protected]> Reviewed-by: Yu Kuai <[email protected]> Reviewed-by: Hannes Reinecke <[email protected]> Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_jpeg.c')
0 files changed, 0 insertions, 0 deletions