summaryrefslogtreecommitdiffstats
path: root/drivers/md/Kconfig
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2017-05-05 19:31:06 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2017-05-05 19:31:06 -0700
commit2eecf3a49f1ff24c6116c954dd74e83f227fc716 (patch)
treec7d51d35106fffb2bea53b7b1cbc7c5a78a4f233 /drivers/md/Kconfig
parent53ef7d0e208fa38c3f63d287e0c3ab174f1e1235 (diff)
parent10add84e276432d9dd8044679a1028dd4084117e (diff)
downloadlinux-2eecf3a49f1ff24c6116c954dd74e83f227fc716.tar.gz
linux-2eecf3a49f1ff24c6116c954dd74e83f227fc716.tar.bz2
linux-2eecf3a49f1ff24c6116c954dd74e83f227fc716.zip
Merge tag 'for-4.12/dm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm
Pull device mapper fixes from Mike Snitzer: - DM cache metadata fixes to short-circuit operations that require the metadata not be in 'fail_io' mode. Otherwise crashes are possible. - a DM cache fix to address the inability to adapt to continuous IO that happened to also reflect a changing working set (which required old blocks be demoted before the new working set could be promoted) - a DM cache smq policy cleanup that fell out from reviewing the above - fix the Kconfig help text for CONFIG_DM_INTEGRITY * tag 'for-4.12/dm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm: dm cache metadata: fail operations if fail_io mode has been established dm integrity: improve the Kconfig help text for DM_INTEGRITY dm cache policy smq: cleanup free_target_met() and clean_target_met() dm cache policy smq: allow demotions to happen even during continuous IO
Diffstat (limited to 'drivers/md/Kconfig')
-rw-r--r--drivers/md/Kconfig15
1 files changed, 13 insertions, 2 deletions
diff --git a/drivers/md/Kconfig b/drivers/md/Kconfig
index 349ff8813401..906103c168ea 100644
--- a/drivers/md/Kconfig
+++ b/drivers/md/Kconfig
@@ -503,13 +503,24 @@ config DM_LOG_WRITES
If unsure, say N.
config DM_INTEGRITY
- tristate "Integrity target"
+ tristate "Integrity target support"
depends on BLK_DEV_DM
select BLK_DEV_INTEGRITY
select DM_BUFIO
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.
+
+ This integrity target is used with the dm-crypt target to
+ provide authenticated disk encryption or it can be used
+ standalone.
+
+ To compile this code as a module, choose M here: the module will
+ be called dm-integrity.
+
+ If unsure, say N.
endif # MD