FAILED: patch "[PATCH] dm zoned: assign max_io_len correctly" failed to apply to 4.19-stable tree
Subsystems (2)
[email protected]
maintainerThe patch below does not apply to the 4.19-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From 7b2377486767503d47265e4d487a63c651f6b55d Mon Sep 17 00:00:00 2001
From: Hou Tao <[email protected]>
Date: Mon, 15 Jun 2020 11:33:23 +0800
Subject: [PATCH] dm zoned: assign max_io_len correctly
The unit of max_io_len is sector instead of byte (spotted through code review), so fix it.
Fixes 3b1a94c88b79 ("dm zoned: drive-managed zoned block device target")
Signed-off-by Hou Tao <[email protected]>
Reviewed-by Damien Le Moal <[email protected]>
Signed-off-by Mike Snitzer <[email protected]>
drivers/md/dm-zoned-target.c +1 -1
@@ -890,7 +890,7 @@ static int dmz_ctr(struct dm_target *ti, unsigned int argc, char **argv) }/* Set target (no write same support) */ - ti->max_io_len =dmz_zone_nr_sectors (dmz->metadata) <<9 ; + ti->max_io_len =dmz_zone_nr_sectors (dmz->metadata); ti->num_flush_bios =1 ; ti->num_discard_bios =1 ; ti->num_write_zeroes_bios =1 ;