[PATCH v3 11/15] block: introduce BLKREPORTZONESV2 ioctl
Damien Le Moal
dlemoal at kernel.org
Tue Nov 4 12:13:45 PST 2025
On 11/5/25 04:00, Bart Van Assche wrote:
> On 11/3/25 5:31 PM, Damien Le Moal wrote:
>> - * @BLKREPORTZONE: Get zone information. Takes a zone report as argument.
>> - * The zone report will start from the zone containing the
>> - * sector specified in the report request structure.
>> + * @BLKREPORTZONE: Get zone information from a zoned device. Takes a zone report
>> + * as argument. The zone report will start from the zone
>> + * containing the sector specified in struct blk_zone_report.
>> + * The flags field of struct blk_zone_report is used as an
>> + * output only and ignored as an input.
>> + * DEPRECATED, use BLKREPORTZONEV2 instead.
>> + * @BLKREPORTZONEV2: Same as @BLKREPORTZONE but uses the flags field of
>> + * struct blk_zone_report as an input, allowing to get a zone
>> + * report using cached zone information if BLK_ZONE_REP_CACHED
>> + * is set.
>
> Was it promised to add information in the above comment about the
> differences in accuracy between the two ioctls? See also
> https://lore.kernel.org/linux-block/97535dde-5902-4f2f-951c-3470d26158da@kernel.org/
As I said, I did. See the comments with the BLK_ZONE_COND_ACTIVE condition.
If you think that is not enough, I can cross reference tht in the comment for
BLKREPORTZONEV2.
--
Damien Le Moal
Western Digital Research
More information about the Linux-nvme
mailing list