The patch titled
Subject: mm, slub, kasan: enable user tracking by default with KASAN=y
has been added to the -mm tree. Its filename is
mm-slub-kasan-enable-user-tracking-by-default-with-kasan=y.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/mm-slub-kasan-enable-user-tracking-by-default-with-kasan%3Dy.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/mm-slub-kasan-enable-user-tracking-by-default-with-kasan%3Dy.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx>
Subject: mm, slub, kasan: enable user tracking by default with KASAN=y
It's recommended to have slub's user tracking enabled with CONFIG_KASAN,
because:
a) User tracking disables slab merging which improves
detecting out-of-bounds accesses.
b) User tracking metadata acts as redzone which also improves
detecting out-of-bounds accesses.
c) User tracking provides additional information about object.
This information helps to understand bugs.
Currently it is not enabled by default. Besides recompiling the kernel
with KASAN and reinstalling it, user also have to change the boot cmdline,
which is not very handy.
Enable slub user tracking by default with KASAN=y, since there is no good
reason to not do this.
Signed-off-by: Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx>
Cc: Christoph Lameter <cl@xxxxxxxxx>
Cc: Pekka Enberg <penberg@xxxxxxxxxx>
Cc: David Rientjes <rientjes@xxxxxxxxxx>
Cc: Joonsoo Kim <iamjoonsoo.kim@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
Documentation/kasan.txt | 3 +--
lib/Kconfig.kasan | 3 +--
mm/slub.c | 2 ++
3 files changed, 4 insertions(+), 4 deletions(-)
diff -puN Documentation/kasan.txt~mm-slub-kasan-enable-user-tracking-by-default-with-kasan=y Documentation/kasan.txt
--- a/Documentation/kasan.txt~mm-slub-kasan-enable-user-tracking-by-default-with-kasan=y
+++ a/Documentation/kasan.txt
@@ -28,8 +28,7 @@ the latter is 1.1 - 2 times faster. Inli
version 5.0 or later.
Currently KASAN works only with the SLUB memory allocator.
-For better bug detection and nicer report, enable CONFIG_STACKTRACE and put
-at least 'slub_debug=U' in the boot cmdline.
+For better bug detection and nicer report and enable CONFIG_STACKTRACE.
To disable instrumentation for specific files or directories, add a line
similar to the following to the respective kernel Makefile:
diff -puN lib/Kconfig.kasan~mm-slub-kasan-enable-user-tracking-by-default-with-kasan=y lib/Kconfig.kasan
--- a/lib/Kconfig.kasan~mm-slub-kasan-enable-user-tracking-by-default-with-kasan=y
+++ a/lib/Kconfig.kasan
@@ -15,8 +15,7 @@ config KASAN
global variables requires gcc 5.0 or later.
This feature consumes about 1/8 of available memory and brings about
~x3 performance slowdown.
- For better error detection enable CONFIG_STACKTRACE,
- and add slub_debug=U to boot cmdline.
+ For better error detection enable CONFIG_STACKTRACE.
choice
prompt "Instrumentation type"
diff -puN mm/slub.c~mm-slub-kasan-enable-user-tracking-by-default-with-kasan=y mm/slub.c
--- a/mm/slub.c~mm-slub-kasan-enable-user-tracking-by-default-with-kasan=y
+++ a/mm/slub.c
@@ -461,6 +461,8 @@ static void get_map(struct kmem_cache *s
*/
#ifdef CONFIG_SLUB_DEBUG_ON
static int slub_debug = DEBUG_DEFAULT_FLAGS;
+#elif defined(CONFIG_KASAN)
+static int slub_debug = SLAB_STORE_USER;
#else
static int slub_debug;
#endif
_
Patches currently in -mm which might be from aryabinin@xxxxxxxxxxxxx are
disable-wframe-larger-than-warnings-with-kasan=y.patch
mm-slub-kasan-enable-user-tracking-by-default-with-kasan=y.patch
kasan-always-taint-kernel-on-report.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
