summaryrefslogtreecommitdiffstats
path: root/drivers/md/dm-vdo/dm-vdo-target.c
diff options
context:
space:
mode:
authorBruce Johnston <bjohnsto@redhat.com>2024-07-09 19:00:36 +0200
committerMikulas Patocka <mpatocka@redhat.com>2024-07-11 21:24:41 +0200
commitd5cfecfe7f3293a4773c4486ac92d742143e8659 (patch)
tree50e75ff973f36efd19585368ddd52913c4801acf /drivers/md/dm-vdo/dm-vdo-target.c
parentdm: always manage discard support in terms of max_hw_discard_sectors (diff)
downloadlinux-d5cfecfe7f3293a4773c4486ac92d742143e8659.tar.xz
linux-d5cfecfe7f3293a4773c4486ac92d742143e8659.zip
dm vdo: replace max_discard_sectors with max_hw_discard_sectors
Commit 4f563a64732d ("block: add a max_user_discard_sectors queue limit") changed block core to set max_discard_sectors to: min(lim->max_hw_discard_sectors, lim->max_user_discard_sectors) Commit 825d8bbd2f32 ("dm: always manage discard support in terms of max_hw_discard_sectors") fixed most dm targetss to deal with this, by replacing max_discard_sectors with max_hw_discard_sectors. Unfortunately, dm-vdo did not get fixed at that time. Fixes: 825d8bbd2f32 ("dm: always manage discard support in terms of max_hw_discard_sectors") Signed-off-by: Bruce Johnston <bjohnsto@redhat.com> Signed-off-by: Matthew Sakai <msakai@redhat.com> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Diffstat (limited to '')
-rw-r--r--drivers/md/dm-vdo/dm-vdo-target.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/md/dm-vdo/dm-vdo-target.c b/drivers/md/dm-vdo/dm-vdo-target.c
index 5a4b0a927f56..af77084969e0 100644
--- a/drivers/md/dm-vdo/dm-vdo-target.c
+++ b/drivers/md/dm-vdo/dm-vdo-target.c
@@ -945,7 +945,7 @@ static void vdo_io_hints(struct dm_target *ti, struct queue_limits *limits)
* The value is used by dm-thin to determine whether to pass down discards. The block layer
* splits large discards on this boundary when this is set.
*/
- limits->max_discard_sectors =
+ limits->max_hw_discard_sectors =
(vdo->device_config->max_discard_blocks * VDO_SECTORS_PER_BLOCK);
/*