protection-information · shipping

Protection information (PI)

Protection information is integrity metadata accompanying storage I/O, with checks determined by the protocol, protection format and participating layers.

A guard check and a location check answer different questions. Do not assume that PI verifies the newest committed generation or application semantics. Describe the configured format and which components generate, preserve and verify it; device capability is not proof of an application-to-media boundary. Linux v6.14 can receive application-supplied PI through io_uring attributes, subject to direct-I/O and lower-layer support. Supplying metadata is distinct from selecting checks. [4] [5]

In the eight-byte PI format, an escape can bypass checking. NVMe 1.4c Type 1/2 use application tag 0xffff; Type 3 requires that tag plus reference tag 0xffffffff. These override PRCHK selection. Do not generalize this historical format to extended PI. [6] Acceptance alone does not establish that a guard was evaluated. [7]

NVMe 1.4c also assigns escape-valued tags to deallocated or unwritten blocks; an escape alone is not a corruption diagnosis. [6] In the tested Linux helper, a metadata prefix adds a second checksum invocation per evaluated interval. The checksum stub tests branching, not accumulated CRC correctness. [7]

Relations

related
End-to-end data protection, Serial Attached SCSI (SAS), NVMe, Misdirected write, Lost write, io_uring integrity metadata, NVMe extended LBA, PI guard tag, PI application tag, PI reference tag, Data Integrity Extensions (DIX)

Citations

  1. Linux v6.14: io_prep_rw_pi, io_prep_rw and io_rw_init_file in io_uring/rw.c. (accessed 2026-10-15)
  2. Linux v6.14: bio_integrity_map_iter and explicit integrity-check flags. (accessed 2026-10-15)
  3. NVM Express Base Specification 1.4c, sections 6.7.1 (p. 260) and 8.3 (p. 319); copyright 2007-2021 NVM Express, Inc., all rights reserved (accessed 2026-10-17)
  4. Hesela: PI escape conditions, source hashes and sixteen control-flow fixtures (accessed 2026-10-17)

Further reading

  1. Linux v6.14: userspace protection-information ABI. (accessed 2026-10-15)
  2. Linux kernel documentation: Data Integrity, protection boundaries and automatic metadata generation. (accessed 2026-10-11)
  3. Hesela: checksum, identity and freshness boundaries with executable synthetic examples (accessed 2026-10-11)
Sources & caveats
  • PI escape evidence is version-scoped: historical NVMe 1.4c plus extracted Linux v6.12 control flow with a checksum stub; not a controller or running-kernel test.
  • The cited experiment executes sixteen selected fixtures, including zero/eight-byte metadata prefixes, against an unchanged verifier with user-space adapters and a fixed-value checksum stub; call counts are not counts of checked intervals.

JSON: /data/terms/protection-information.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Protection information (PI). Hesela. 2026-11-13. https://hesela.dev/terms/protection-information/