On 5/31/24 6:03 AM, Jens Axboe wrote: > On 5/29/24 11:40 PM, Damien Le Moal wrote: >> 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. > > Would be nice to get the dm part acked, but I guess I can queue up 1-3 > for now for 6.10? Yes please. Mike, Mikulas, Could you please review patch 4 ? It is a long standing issue with DM but now that zone write plugging fakes a smaller 128 max open zones limit for drives with no limits, zonefs gets confused and tests fail. So it would be great to get this patch in for 6.10 as a fix. Thanks ! -- Damien Le Moal Western Digital Research
