From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E9A594E3ED9; Fri, 9 Oct 2026 14:30:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791556210; cv=none; b=aBy5SaSKYD896dipCvlfQuJ/VZSEzaeC5fgXp0QGAnxe9FchKyy19RwFCmzwNqv7NcIsjMWhr8T0cmOsJ3Kdc/62O+yOmbiqu1e+9wN5dIKZCJMsuHYAxBl6Sf9HK/d6hMcBDy3LWhEUPCrixzQxvJ4DbvaeJ4PRjAXopiBYHEU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791556210; c=relaxed/simple; bh=mkh9iMmDqkR69cM+FiFXopGXvnXWH6ltPCQrmf2Yd08=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=RdaXOGM/kGdYsLe9RkMa6gxYebwVgfYmY7iWbvvk3OG0x75EtkyOMrea3+1nEUoYuiY81IBD7mKZPQPIMitTc63DNjDIEdcLiSQMxb3ZbRUK0ED5GxMKehexXXZKBlT38SiRCfhGr4nNDw79dVqy4J0HVSCHhQqhxx8JFk9iiQ4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=k4+sfXyz; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="k4+sfXyz" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4D2F21F000FF; Fri, 9 Oct 2026 14:30:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1791556209; bh=NrD0t0s17LUDcNkggVXg1+0yhusv8G48aL57KUZWqtA=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=k4+sfXyzn4+DXu9VmD45FwJIKZ4QuaZ3H1p5Ju9Bo6WcDqtoezKZRwjSOEEXBuzYw /+waQVT45+EjmWG9yU6yO5C3BZSynaq3kQVUCvrGqLhY7m6RKT9KAPMQr0kP7cHuyv 4j2RuFHXfTtHkOSYcF52z6ZZdHShz6RtE8GgBo+4= From: Greg Kroah-Hartman To: stable@vger.kernel.org Cc: Greg Kroah-Hartman , patches@lists.linux.dev, Niklas Cassel , Stefan Hajnoczi , Jens Axboe , Sasha Levin Subject: [PATCH 7.2 138/428] virtio_blk: set the zone write granularity Date: Fri, 9 Oct 2026 16:07:55 +0200 Message-ID: <20261009140949.210783306@linuxfoundation.org> X-Mailer: git-send-email 2.56.0 In-Reply-To: <20261009140946.008206689@linuxfoundation.org> References: <20261009140946.008206689@linuxfoundation.org> User-Agent: quilt/0.69 X-stable: review X-Patchwork-Hint: ignore Precedence: bulk X-Mailing-List: patches@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 7.2-stable review patch. If anyone has any objections, please let me know. ------------------ From: Niklas Cassel [ Upstream commit 684b413b5483f57c890c171b9400076a0143b918 ] virtblk_read_zoned_limits() reads the write granularity that the device reports in virtio_blk_zoned_characteristics and assigns it to the physical block size and to io_min, but never to the limit that is named after it. queue_limits.zone_write_granularity is left at zero, so blk_validate_zoned_limits() raises it to the logical block size: if (lim->zone_write_granularity < lim->logical_block_size) lim->zone_write_granularity = lim->logical_block_size; A device that reports a granularity coarser than its logical block size, which is what the field exists to express, therefore has it silently reduced. A 512e host managed disk passed through to a guest reports a logical block size of 512 and a write granularity of 4096, and the guest ends up with a zone write granularity of 512. bio_split_alignment() returns lim->zone_write_granularity if it is non-zero and bio_split_io_at() may split a bio with as per bio_split_alignment(). This can real to the write getting rejected by the host drive, as the write is not aligned to the physical block size. zonefs also takes its block size from bdev_zone_write_granularity(), so it would incorrectly use 512 on a disk that requires 4096. sd_zbc_read_zones() sets the limit from the physical block size for the same reason. NVMe ZNS and null_blk leave it unset, but the fallback gives the right answer for them, as their write granularity is the logical block size. virtio carries a separate value that may exceed it. Set the zone write granularity from the value that the device reports. Fixes: 95bfec41bd3d ("virtio-blk: add support for zoned block devices") Signed-off-by: Niklas Cassel Reviewed-by: Stefan Hajnoczi Link: https://patch.msgid.link/20260918140641.2031075-2-cassel@kernel.org Signed-off-by: Jens Axboe Signed-off-by: Sasha Levin --- drivers/block/virtio_blk.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c index 32bf3ba07a9dc..c8bfbf8435ac7 100644 --- a/drivers/block/virtio_blk.c +++ b/drivers/block/virtio_blk.c @@ -743,6 +743,7 @@ static int virtblk_read_zoned_limits(struct virtio_blk *vblk, dev_warn(&vdev->dev, "zero write granularity reported\n"); return -ENODEV; } + lim->zone_write_granularity = wg; lim->physical_block_size = wg; lim->io_min = wg; -- 2.53.0