The first patch of this series fixes null_blk to avoid weird zone configurations, namely, a zoned device with a last smaller zone with a zone capacity smaller than the zone size. Related to this, the next 2 patches fix the handling by zone write plugging of zoned devices with a last smaller zone. That was completely botched in the initial series. Finally, the last patch addresses a long standing issue with zoned device-mapper devices: no zone resource limits (max open and max active zones limits) are not exposed to the user. This patch fixes that, allowing for the limits of the underlying target devices to be exposed with a warning for setups that lead to unreliable limits. This is all based on block/block-6.10 branch and the last patch depends on Christoph's recent DM queue limits fixes. While the last patch is technically not really a fix for a recent bug, it would be nice to get it in this cycle as the change in the max open zone limits introduced with zone write plugging (i.e. expose a imax open zone limit of 128 for devices with no open zones limits) is confusing zonefs tests causing failures. Damien Le Moal (4): null_blk: Do not allow runt zone with zone capacity smaller then zone size block: Fix validation of zoned device with a runt zone block: Fix zone write plugging handling of devices with a runt zone dm: Improve zone resource limits handling block/blk-zoned.c | 47 ++++++-- drivers/block/null_blk/zoned.c | 11 ++ drivers/md/dm-zone.c | 214 +++++++++++++++++++++++++++------ include/linux/blkdev.h | 1 + 4 files changed, 225 insertions(+), 48 deletions(-) -- 2.45.1
