diff mbox series

[v2,5/5] libnvdimm: add documentation for ovewrite

Message ID 153817471166.19407.8554249441903250990.stgit@djiang5-desk3.ch.intel.com (mailing list archive)
State New, archived
Headers show
Series Adding nvdimm overwrite support | expand

Commit Message

Dave Jiang Sept. 28, 2018, 10:45 p.m. UTC
Add overwrite command usages to security documentation.

Signed-off-by: Dave Jiang <dave.jiang@intel.com>
 Documentation/nvdimm/security.txt |   11 +++++++++++
 1 file changed, 11 insertions(+)
diff mbox series


diff --git a/Documentation/nvdimm/security.txt b/Documentation/nvdimm/security.txt
index 50cbb6cb96a1..ded5f0e3f7c3 100644
--- a/Documentation/nvdimm/security.txt
+++ b/Documentation/nvdimm/security.txt
@@ -91,6 +91,17 @@  its keyid should be passed in via sysfs.
 The command format for doing a secure erase is:
 erase <old keyid>
+9. Overwrite
+The command format for doing an overwrite is:
+overwrite <old keyid>
+Overwrite can be done without a key if security is not enabled. A key serial
+of 0 can be passed in to indicate no key.
+The sysfs attribute "security" can be polled to wait on overwrite completion.
+Overwrite can last tens of minutes or more depending on nvdimm size.
 An "old" key with the passphrase payload that is tied to the nvdimm should be
 injected with a key description that does not have the "nvdimm:" prefix and
 its keyid should be passed in via sysfs.