From: Kees Cook <keescook@chromium.org>
To: akpm@linux-foundation.org
Cc: Kees Cook <keescook@chromium.org>,
Vlastimil Babka <vbabka@suse.cz>, Roman Gushchin <guro@fb.com>,
Christoph Lameter <cl@linux.com>,
Alexander Popov <alex.popov@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
vinmenon@codeaurora.org, Matthew Garrett <mjg59@google.com>,
Jann Horn <jannh@google.com>,
Vijayanand Jitta <vjitta@codeaurora.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] mm: Expand CONFIG_SLAB_FREELIST_HARDENED to include SLAB
Date: Thu, 25 Jun 2020 14:55:46 -0700 [thread overview]
Message-ID: <20200625215548.389774-1-keescook@chromium.org> (raw)
Hi,
In reviewing Vlastimil Babka's latest slub debug series, I realized[1]
that several checks under CONFIG_SLAB_FREELIST_HARDENED weren't being
applied to SLAB. Fix this by expanding the Kconfig coverage, and
adding a simple double-free test for SLAB.
v2:
- rebase to -mmots
- drop SLOB support (willy)
v1: https://lore.kernel.org/lkml/20200617195349.3471794-1-keescook@chromium.org/
Thanks!
-Kees
[1] https://lore.kernel.org/lkml/202006171039.FBDF2D7F4A@keescook/
Kees Cook (2):
mm: Expand CONFIG_SLAB_FREELIST_HARDENED to include SLAB
slab: Add naive detection of double free
init/Kconfig | 9 +++++----
mm/slab.c | 14 ++++++++++++--
2 files changed, 17 insertions(+), 6 deletions(-)
--
2.25.1
next reply other threads:[~2020-06-25 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 21:55 Kees Cook [this message]
2020-06-25 21:55 ` [PATCH v2 1/2] " Kees Cook
2020-08-04 17:15 ` Vlastimil Babka
2020-06-25 21:55 ` [PATCH v2 2/2] slab: Add naive detection of double free Kees Cook
2020-08-04 17:18 ` Vlastimil Babka
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=20200625215548.389774-1-keescook@chromium.org \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=alex.popov@linux.com \
--cc=cl@linux.com \
--cc=guro@fb.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mjg59@google.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--cc=vinmenon@codeaurora.org \
--cc=vjitta@codeaurora.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox