From: Kees Cook <keescook@chromium.org> To: Peter Zijlstra <peterz@infradead.org> Cc: Kees Cook <keescook@chromium.org>, elena.reshetova@intel.com, gregkh@linuxfoundation.org, arnd@arndb.de, tglx@linutronix.de, mingo@kernel.org, h.peter.anvin@intel.com, will.deacon@arm.com, dwindsor@gmail.com, Hans Liljestrand <ishkamiel@gmail.com>, dhowells@redhat.com, linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com Subject: [PATCH 1/4] refcount_t: fix Kconfig help Date: Fri, 3 Feb 2017 15:26:49 -0800 [thread overview] Message-ID: <1486164412-7338-2-git-send-email-keescook@chromium.org> (raw) In-Reply-To: <1486164412-7338-1-git-send-email-keescook@chromium.org> Minor fix to build refcount_t series. Signed-off-by: Kees Cook <keescook@chromium.org> --- lib/Kconfig.debug | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index 6f61d32ee536..20fde8d4523a 100644 --- a/lib/Kconfig.debug +++ b/lib/Kconfig.debug @@ -731,7 +731,7 @@ source "lib/Kconfig.kasan" config DEBUG_REFCOUNT bool "Verbose refcount checks" - --help-- + help Say Y here if you want reference counters (refcount_t and kref) to generate WARNs on dubious usage. Without this refcount_t will still be a saturating counter and avoid Use-After-Free by turning it into -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org> To: Peter Zijlstra <peterz@infradead.org> Cc: Kees Cook <keescook@chromium.org>, elena.reshetova@intel.com, gregkh@linuxfoundation.org, arnd@arndb.de, tglx@linutronix.de, mingo@kernel.org, h.peter.anvin@intel.com, will.deacon@arm.com, dwindsor@gmail.com, Hans Liljestrand <ishkamiel@gmail.com>, dhowells@redhat.com, linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com Subject: [kernel-hardening] [PATCH 1/4] refcount_t: fix Kconfig help Date: Fri, 3 Feb 2017 15:26:49 -0800 [thread overview] Message-ID: <1486164412-7338-2-git-send-email-keescook@chromium.org> (raw) In-Reply-To: <1486164412-7338-1-git-send-email-keescook@chromium.org> Minor fix to build refcount_t series. Signed-off-by: Kees Cook <keescook@chromium.org> --- lib/Kconfig.debug | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index 6f61d32ee536..20fde8d4523a 100644 --- a/lib/Kconfig.debug +++ b/lib/Kconfig.debug @@ -731,7 +731,7 @@ source "lib/Kconfig.kasan" config DEBUG_REFCOUNT bool "Verbose refcount checks" - --help-- + help Say Y here if you want reference counters (refcount_t and kref) to generate WARNs on dubious usage. Without this refcount_t will still be a saturating counter and avoid Use-After-Free by turning it into -- 2.7.4
next prev parent reply other threads:[~2017-02-03 23:27 UTC|newest] Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-02-03 23:26 [PATCH 0/4] refcount_t followups Kees Cook 2017-02-03 23:26 ` [kernel-hardening] " Kees Cook 2017-02-03 23:26 ` Kees Cook [this message] 2017-02-03 23:26 ` [kernel-hardening] [PATCH 1/4] refcount_t: fix Kconfig help Kees Cook 2017-02-03 23:26 ` [PATCH 2/4] lkdtm: convert to refcount_t testing Kees Cook 2017-02-03 23:26 ` [kernel-hardening] " Kees Cook 2017-02-10 8:32 ` [tip:locking/core] lkdtm: Convert " tip-bot for Kees Cook 2017-02-03 23:26 ` [PATCH 3/4] bug: Switch data corruption check to __must_check Kees Cook 2017-02-03 23:26 ` [kernel-hardening] " Kees Cook 2017-02-03 23:26 ` [PATCH 4/4] refcount: Report failures through CHECK_DATA_CORRUPTION Kees Cook 2017-02-03 23:26 ` [kernel-hardening] " Kees Cook 2017-02-05 15:40 ` Peter Zijlstra 2017-02-05 15:40 ` [kernel-hardening] " Peter Zijlstra 2017-02-05 23:33 ` Kees Cook 2017-02-05 23:33 ` [kernel-hardening] " Kees Cook 2017-02-06 8:57 ` Peter Zijlstra 2017-02-06 8:57 ` [kernel-hardening] " Peter Zijlstra 2017-02-06 16:54 ` Kees Cook 2017-02-06 16:54 ` [kernel-hardening] " Kees Cook 2017-02-07 8:34 ` Peter Zijlstra 2017-02-07 8:34 ` [kernel-hardening] " Peter Zijlstra 2017-02-07 11:10 ` Mark Rutland 2017-02-07 11:10 ` Mark Rutland 2017-02-07 12:36 ` Peter Zijlstra 2017-02-07 12:36 ` Peter Zijlstra 2017-02-07 13:50 ` Mark Rutland 2017-02-07 13:50 ` Mark Rutland 2017-02-07 15:07 ` Peter Zijlstra 2017-02-07 15:07 ` Peter Zijlstra 2017-02-07 16:03 ` Mark Rutland 2017-02-07 16:03 ` Mark Rutland 2017-02-07 17:30 ` Peter Zijlstra 2017-02-07 17:30 ` Peter Zijlstra 2017-02-07 17:55 ` Mark Rutland 2017-02-07 17:55 ` Mark Rutland 2017-02-08 9:12 ` Peter Zijlstra 2017-02-08 9:12 ` Peter Zijlstra 2017-02-08 9:43 ` Peter Zijlstra 2017-02-08 9:43 ` Peter Zijlstra 2017-02-08 14:10 ` Mark Rutland 2017-02-08 14:10 ` Mark Rutland 2017-02-08 21:20 ` Kees Cook 2017-02-08 21:20 ` Kees Cook 2017-02-09 10:27 ` Peter Zijlstra 2017-02-09 10:27 ` Peter Zijlstra 2017-02-10 23:39 ` Kees Cook 2017-02-10 23:39 ` Kees Cook
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=1486164412-7338-2-git-send-email-keescook@chromium.org \ --to=keescook@chromium.org \ --cc=arnd@arndb.de \ --cc=dhowells@redhat.com \ --cc=dwindsor@gmail.com \ --cc=elena.reshetova@intel.com \ --cc=gregkh@linuxfoundation.org \ --cc=h.peter.anvin@intel.com \ --cc=ishkamiel@gmail.com \ --cc=kernel-hardening@lists.openwall.com \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=peterz@infradead.org \ --cc=tglx@linutronix.de \ --cc=will.deacon@arm.com \ /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.