Document:
03675: Resolve Issue #125: virtio-blk: add secure erase feature to specification

Draft (A preliminary unapproved sketch, outline, or version.)

Details

Submitted By Ms. Cornelia Huck on 2021-12-20 3:33 pm UTC

Publication Type

None at this time.

Group / Folder

OASIS Virtual I/O Device (VIRTIO) TC / System Ballot Results

Modified by

Not modified.

Copy

This document is not a copy.

Technical Contact

None at this time.

Download Count

148

Download Agreement

None at this time.

Description

Please vote Yes if you agree with all of the following. If you disagree, please vote No. If you don't have an opinion, please vote Abstain. I move that: The TC agrees to resolve the following specification issue: Issue #125: virtio-blk: add secure erase feature to specification -------------------------------------- There are user requests to use the Linux BLKSECDISCARD ioctl on virtio-blk device. A secure discard is the same as a regular discard except that all copies of the discarded blocks that were possibly created by garbage collection must also be erased. This requires support from the device. And "secure erase" is more commonly used in industry to name this feature. Hence in this proposal, extend virtio-blk protocol to support secure erase command. Introduced new feature flag and command type: VIRTIO_BLK_F_SECURE_ERASE VIRTIO_BLK_T_SECURE_ERASE This feature is a passthrough feature on backend because it is hard to emulate a secure erase. So virtio-blk will report this feature to guest OS if backend device support such kind of feature. And when guest OS issues a secure erase command, backend driver will passthrough the command to host device blocks. Introduced new fields in virtio_blk_config for secure erase commands: struct virtio_blk_config { ... max_secure_erase_sectors; max_secure_erase_seg; secure_erase_sector_alignment; }; https://lists.oasis-open.org/archives/virtio-comment/202112/msg00020.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/202112/msg00020.html -------------------------------------- The TC agrees to include the above change(s) in specification version(s) "virtio-v1.2-cs01", and future versions of the specification. -------------------------------------- Reminder: A Voting Member must be active in a TC to maintain voting rights. As the Virtio TC has adopted a standing rule to conduct business only by electronic ballot, without Meetings, a Voting Member who fails to cast a ballot in two consecutive Work Product Ballots loses his or her voting rights at the close of the second ballot missed. --------------------------------------