From: Alexander Potapenko <glider@google.com>
To: adech.fo@gmail.com, cl@linux.com, dvyukov@google.com,
akpm@linux-foundation.org, rostedt@goodmis.org,
iamjoonsoo.kim@lge.com, js1304@gmail.com, kcc@google.com,
aryabinin@virtuozzo.com, kuthonuzo.luruo@hpe.com
Cc: kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v7 0/2] mm, kasan: stackdepot and quarantine for SLUB
Date: Tue, 12 Jul 2016 20:12:43 +0200 [thread overview]
Message-ID: <1468347165-41906-1-git-send-email-glider@google.com> (raw)
This patch set enables stackdepot and quarantine for SLUB allocator and
fixes a problem with incorrect calculating the offset of the nearest
object in the presence of SLUB red zones.
Alexander Potapenko (2):
mm, kasan: account for object redzone in SLUB's nearest_obj()
mm, kasan: switch SLUB to stackdepot, enable memory quarantine for
SLUB
include/linux/kasan.h | 2 ++
include/linux/slab_def.h | 3 ++-
include/linux/slub_def.h | 14 ++++++++---
lib/Kconfig.kasan | 4 +--
mm/kasan/Makefile | 3 +--
mm/kasan/kasan.c | 64 +++++++++++++++++++++++++++---------------------
mm/kasan/kasan.h | 3 +--
mm/kasan/report.c | 8 +++---
mm/slab.h | 2 ++
mm/slub.c | 59 +++++++++++++++++++++++++++++++++-----------
10 files changed, 104 insertions(+), 58 deletions(-)
--
2.8.0.rc3.226.g39d4020
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2016-07-12 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 18:12 Alexander Potapenko [this message]
2016-07-12 18:12 ` [PATCH v7 1/2] mm, kasan: account for object redzone in SLUB's nearest_obj() Alexander Potapenko
2016-07-12 20:02 ` Andrew Morton
2016-07-13 12:14 ` Alexander Potapenko
2016-07-12 18:12 ` [PATCH v7 2/2] mm, kasan: switch SLUB to stackdepot, enable memory quarantine for SLUB Alexander Potapenko
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=1468347165-41906-1-git-send-email-glider@google.com \
--to=glider@google.com \
--cc=adech.fo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=cl@linux.com \
--cc=dvyukov@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=kasan-dev@googlegroups.com \
--cc=kcc@google.com \
--cc=kuthonuzo.luruo@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).