On 2020/06/29 20:38, gregkh@linuxfoundation.org wrote:

The patch below does not apply to the 5.4-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 stable@vger.kernel.org.

thanks,

Greg,

I just sent to you and stable@vger.kernel.org a fixed patch that cleanly applies to 5.7.y, 5.4.y, 4.19.y and 4.14.y.

Thanks !

greg k-h

------------------ original commit in Linus's tree ------------------

From 7b2377486767503d47265e4d487a63c651f6b55d Mon Sep 17 00:00:00 2001 From: Hou Tao houtao1@huawei.com 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") Cc: stable@vger.kernel.org Signed-off-by: Hou Tao houtao1@huawei.com Reviewed-by: Damien Le Moal damien.lemoal@wdc.com Signed-off-by: Mike Snitzer snitzer@redhat.com

diff --git a/drivers/md/dm-zoned-target.c b/drivers/md/dm-zoned-target.c index a907a9446c0b..cf915009c306 100644 --- a/drivers/md/dm-zoned-target.c +++ b/drivers/md/dm-zoned-target.c @@ -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;