diff mbox

dm-integrity: Add proper description of module to KConfig.

Message ID 20170504075044.5766-1-gmazyland@gmail.com (mailing list archive)
State Accepted, archived
Delegated to: Mike Snitzer
Headers show

Commit Message

Milan Broz May 4, 2017, 7:50 a.m. UTC 
Add more descriptive text to explain what it the dm-integrity
when it should be enabled.

Signed-off-by: Milan Broz <gmazyland@gmail.com>
---
 drivers/md/Kconfig | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)
diff mbox

Patch

diff --git a/drivers/md/Kconfig b/drivers/md/Kconfig
index 7468a22f9d10..3e96fccbbdb2 100644
--- a/drivers/md/Kconfig
+++ b/drivers/md/Kconfig
@@ -509,6 +509,20 @@  config DM_INTEGRITY
 	select CRYPTO
 	select ASYNC_XOR
 	---help---
-	   This is the integrity target.
+	  This device-mapper target emulates a block device that has additional
+	  per-sector tags that can be used for storing integrity information.
+
+	  The dm-integrity target is used with the dm-crypt target to provide
+	  authenticated disk encryption or it can also be used as a standalone
+	  target. In standalone mode it calculates and verifies the data integrity
+	  internally.
+
+	  You should enable this option if you plan to use dm-crypt target
+	  in authenticated disk encryption mode.
+
+	  To compile this code as a module, choose M here: the module will
+	  be called dm-integrity.
+
+	  If unsure, say N.
 
 endif # MD