| 1 |
.TH "libnvme" 9 "enum nvme_cmd_format_ses" "November 2025" "API Manual" LINUX |
| 2 |
.SH NAME |
| 3 |
enum nvme_cmd_format_ses \- Format NVM - Secure Erase Settings |
| 4 |
.SH SYNOPSIS |
| 5 |
enum nvme_cmd_format_ses { |
| 6 |
.br |
| 7 |
.BI " NVME_FORMAT_SES_NONE" |
| 8 |
, |
| 9 |
.br |
| 10 |
.br |
| 11 |
.BI " NVME_FORMAT_SES_USER_DATA_ERASE" |
| 12 |
, |
| 13 |
.br |
| 14 |
.br |
| 15 |
.BI " NVME_FORMAT_SES_CRYPTO_ERASE" |
| 16 |
|
| 17 |
}; |
| 18 |
.SH Constants |
| 19 |
.IP "NVME_FORMAT_SES_NONE" 12 |
| 20 |
No secure erase operation requested. |
| 21 |
.IP "NVME_FORMAT_SES_USER_DATA_ERASE" 12 |
| 22 |
User Data Erase: All user data shall be erased, |
| 23 |
contents of the user data after the erase is |
| 24 |
indeterminate (e.g. the user data may be zero |
| 25 |
filled, one filled, etc.). If a User Data Erase |
| 26 |
is requested and all affected user data is |
| 27 |
encrypted, then the controller is allowed |
| 28 |
to use a cryptographic erase to perform |
| 29 |
the requested User Data Erase. |
| 30 |
.IP "NVME_FORMAT_SES_CRYPTO_ERASE" 12 |
| 31 |
Cryptographic Erase: All user data shall |
| 32 |
be erased cryptographically. This is |
| 33 |
accomplished by deleting the encryption key. |