From: Christoph Hellwig Date: Fri, 8 Nov 2024 15:46:52 +0000 (+0100) Subject: nvme-multipath: don't bother clearing max_hw_zone_append_sectors X-Git-Tag: v6.13-rc1~211^2~14 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=0b4ace9da58df62c1763635ab10ae1bc8ed8182a;p=thirdparty%2Fkernel%2Flinux.git nvme-multipath: don't bother clearing max_hw_zone_append_sectors The limits stacking now properly zeroes it if at least one of the underlying limits clears it. Signed-off-by: Christoph Hellwig Reviewed-by: Damien Le Moal Link: https://lore.kernel.org/r/20241108154657.845768-3-hch@lst.de Signed-off-by: Jens Axboe --- diff --git a/drivers/nvme/host/multipath.c b/drivers/nvme/host/multipath.c index c26cb7d3a2e55..f04cfe3fb936c 100644 --- a/drivers/nvme/host/multipath.c +++ b/drivers/nvme/host/multipath.c @@ -635,8 +635,6 @@ int nvme_mpath_alloc_disk(struct nvme_ctrl *ctrl, struct nvme_ns_head *head) lim.features |= BLK_FEAT_IO_STAT | BLK_FEAT_NOWAIT | BLK_FEAT_POLL; if (head->ids.csi == NVME_CSI_ZNS) lim.features |= BLK_FEAT_ZONED; - else - lim.max_hw_zone_append_sectors = 0; head->disk = blk_alloc_disk(&lim, ctrl->numa_node); if (IS_ERR(head->disk))