Since CONFIG_DEBUG_CREDENTIALS already handles reporting and issuing a BUG when it encounters corruption, add this to the list of corruption test CONFIGs that are enabled under CONFIG_BUG_ON_DATA_CORRUPTION.
Signed-off-by: Kees Cook <keesc...@chromium.org> --- lib/Kconfig.debug | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index 5ac4d1148385..9a1b6b56cef4 100644 --- a/lib/Kconfig.debug +++ b/lib/Kconfig.debug @@ -1288,7 +1288,7 @@ config DEBUG_NOTIFIERS config DEBUG_CREDENTIALS bool "Debug credential management" - depends on DEBUG_KERNEL + depends on DEBUG_KERNEL || BUG_ON_DATA_CORRUPTION help Enable this to turn on some debug checking for credential management. The additional code keeps track of the number of @@ -1996,6 +1996,7 @@ config TEST_STATIC_KEYS config BUG_ON_DATA_CORRUPTION bool "Trigger a BUG when data corruption is detected" + select DEBUG_CREDENTIALS select DEBUG_LIST help This option enables several inexpensive data corruption checks. -- 2.7.4