From: Kees Cook <keescook@chromium.org> To: Ingo Molnar <mingo@kernel.org> Cc: Kees Cook <keescook@chromium.org>, Peter Zijlstra <peterz@infradead.org>, "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>, Kalle Valo <kvalo@codeaurora.org>, Andrew Morton <akpm@linux-foundation.org>, Rik van Riel <riel@redhat.com>, Jakub Kicinski <jakub.kicinski@netronome.com>, Viresh Kumar <viresh.kumar@linaro.org>, Andy Shevchenko <andriy.shevchenko@linux.intel.com>, Geert Uytterhoeven <geert@linux-m68k.org>, Olof Johansson <olof@lixom.net>, Chris Wilson <chris@chris-wilson.co.uk>, George Spelvin <linux@sciencehorizons.net>, Thomas Gleixner <tglx@linutronix.de>, Josh Poimboeuf <jpoimboe@redhat.com>, David Windsor <dwindsor@gmail.com>, linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com Subject: [PATCH v2 4/7] bug: Enable DEBUG_CREDENTIALS under BUG_ON_DATA_CORRUPTION Date: Tue, 4 Apr 2017 15:12:15 -0700 [thread overview] Message-ID: <1491343938-75336-5-git-send-email-keescook@chromium.org> (raw) In-Reply-To: <1491343938-75336-1-git-send-email-keescook@chromium.org> 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 <keescook@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
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org> To: Ingo Molnar <mingo@kernel.org> Cc: Kees Cook <keescook@chromium.org>, Peter Zijlstra <peterz@infradead.org>, "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>, Kalle Valo <kvalo@codeaurora.org>, Andrew Morton <akpm@linux-foundation.org>, Rik van Riel <riel@redhat.com>, Jakub Kicinski <jakub.kicinski@netronome.com>, Viresh Kumar <viresh.kumar@linaro.org>, Andy Shevchenko <andriy.shevchenko@linux.intel.com>, Geert Uytterhoeven <geert@linux-m68k.org>, Olof Johansson <olof@lixom.net>, Chris Wilson <chris@chris-wilson.co.uk>, George Spelvin <linux@sciencehorizons.net>, Thomas Gleixner <tglx@linutronix.de>, Josh Poimboeuf <jpoimboe@redhat.com>, David Windsor <dwindsor@gmail.com>, linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com Subject: [kernel-hardening] [PATCH v2 4/7] bug: Enable DEBUG_CREDENTIALS under BUG_ON_DATA_CORRUPTION Date: Tue, 4 Apr 2017 15:12:15 -0700 [thread overview] Message-ID: <1491343938-75336-5-git-send-email-keescook@chromium.org> (raw) In-Reply-To: <1491343938-75336-1-git-send-email-keescook@chromium.org> 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 <keescook@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
next prev parent reply other threads:[~2017-04-04 22:12 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-04-04 22:12 [PATCH v2] bug: further enhance use of CHECK_DATA_CORRUPTION Kees Cook 2017-04-04 22:12 ` [kernel-hardening] " Kees Cook 2017-04-04 22:12 ` [PATCH v2 1/7] bug: Clarify help text for BUG_ON_DATA_CORRUPTION Kees Cook 2017-04-04 22:12 ` [kernel-hardening] " Kees Cook 2017-04-05 5:47 ` Ian Campbell 2017-04-05 19:32 ` Kees Cook 2017-04-05 19:32 ` Kees Cook 2017-04-04 22:12 ` [PATCH v2 2/7] bug: Improve unlikely() in data corruption check Kees Cook 2017-04-04 22:12 ` [kernel-hardening] " Kees Cook 2017-04-04 22:12 ` [PATCH v2 3/7] bug: Use WARN_ONCE() for CHECK_DATA_CORRUPTION() Kees Cook 2017-04-04 22:12 ` [kernel-hardening] " Kees Cook 2017-04-04 22:12 ` Kees Cook [this message] 2017-04-04 22:12 ` [kernel-hardening] [PATCH v2 4/7] bug: Enable DEBUG_CREDENTIALS under BUG_ON_DATA_CORRUPTION Kees Cook 2017-04-04 22:12 ` [PATCH v2 5/7] bug: Enable DEBUG_SG " Kees Cook 2017-04-04 22:12 ` [kernel-hardening] " Kees Cook 2017-04-04 22:12 ` [PATCH v2 6/7] notifiers: Use CHECK_DATA_CORRUPTION() on checks Kees Cook 2017-04-04 22:12 ` [kernel-hardening] " Kees Cook 2017-04-04 22:12 ` [PATCH v2 7/7] refcount: Check bad states with CHECK_DATA_CORRUPTION() Kees Cook 2017-04-04 22:12 ` [kernel-hardening] " Kees Cook 2021-01-04 23:07 ` [PATCH v2] bug: further enhance use of CHECK_DATA_CORRUPTION Josh Poimboeuf
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1491343938-75336-5-git-send-email-keescook@chromium.org \ --to=keescook@chromium.org \ --cc=akpm@linux-foundation.org \ --cc=andriy.shevchenko@linux.intel.com \ --cc=chris@chris-wilson.co.uk \ --cc=dwindsor@gmail.com \ --cc=geert@linux-m68k.org \ --cc=jakub.kicinski@netronome.com \ --cc=jpoimboe@redhat.com \ --cc=kernel-hardening@lists.openwall.com \ --cc=kvalo@codeaurora.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@sciencehorizons.net \ --cc=mingo@kernel.org \ --cc=olof@lixom.net \ --cc=paulmck@linux.vnet.ibm.com \ --cc=peterz@infradead.org \ --cc=riel@redhat.com \ --cc=tglx@linutronix.de \ --cc=viresh.kumar@linaro.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.