On 2021/01/28 18:24, Christoph Hellwig wrote: > On Thu, Jan 28, 2021 at 01:47:33PM +0900, Damien Le Moal wrote: >> For host-aware ZBC disk, setting the device zoned model to BLK_ZONED_HA >> using blk_queue_set_zoned() in sd_read_block_characteristics() may >> result in the block device effective zoned model to be "none" >> (BLK_ZONED_NONE) if partitions are present on the device. In this case, >> sd_zbc_read_zones() should not setup the zone related queue limits for >> the disk so that the device limits and configuration is consistent with >> a regular disk and resources not uselessly allocated (e.g. the zone >> write pointer tracking array for zone append emulation). >> >> Furthermore, if the disk zoned model changes at run time due to the >> creation of a partition by the user, the zone related resources can be >> released. >> >> Fix both problems by introducing the function sd_zbc_clear_zone_info() >> to reset the scsi disk zone information and free resources and by >> returning early in sd_zbc_read_zones() for a block device that has a >> zoned model equal to BLK_ZONED_NONE. > > So creating the partition doesn't even call into the driver, which > means we'll leak the info for now. But I guess the next revalidate > will simply clean it up, so it is not a major issue. Exactly. But the leak is only for the sd level resources now. blk_queue_set_zoned() cleans up everything else. The super annoying thing is that deleting all partitions leaves that disk in regular mode instead of returning it to zoned mode. Need to wait for a revalidate or for a manual rescan for that to happen. I wonder if we should not trigger a revalidate, always, to avoid that the user sees the device type suddenly changing long after the partitions were deleted... Adding such revalidate for partition creation would solve the "leak" problem (or rather the lack of cleaning) too. > > Looks good: > > Reviewed-by: Christoph Hellwig <hch@xxxxxx> > -- Damien Le Moal Western Digital Research
