|author||Andrey Ryabinin <email@example.com>||2019-03-05 15:41:20 -0800|
|committer||Linus Torvalds <firstname.lastname@example.org>||2019-03-05 21:07:13 -0800|
kasan: remove use after scope bugs detection.
Use after scope bugs detector seems to be almost entirely useless for the linux kernel. It exists over two years, but I've seen only one valid bug so far . And the bug was fixed before it has been reported. There were some other use-after-scope reports, but they were false-positives due to different reasons like incompatibility with structleak plugin. This feature significantly increases stack usage, especially with GCC < 9 version, and causes a 32K stack overflow. It probably adds performance penalty too. Given all that, let's remove use-after-scope detector entirely. While preparing this patch I've noticed that we mistakenly enable use-after-scope detection for clang compiler regardless of CONFIG_KASAN_EXTRA setting. This is also fixed now.  http://lkml.kernel.org/r/<email@example.com> Link: http://firstname.lastname@example.org Signed-off-by: Andrey Ryabinin <email@example.com> Acked-by: Will Deacon <firstname.lastname@example.org> [arm64] Cc: Qian Cai <email@example.com> Cc: Alexander Potapenko <firstname.lastname@example.org> Cc: Dmitry Vyukov <email@example.com> Cc: Catalin Marinas <firstname.lastname@example.org> Signed-off-by: Andrew Morton <email@example.com> Signed-off-by: Linus Torvalds <firstname.lastname@example.org>
Diffstat (limited to 'scripts/gcc-plugins')
1 files changed, 0 insertions, 4 deletions
diff --git a/scripts/gcc-plugins/Kconfig b/scripts/gcc-plugins/Kconfig
index d45f7f36b859..d9fd9988ef27 100644
@@ -68,10 +68,6 @@ config GCC_PLUGIN_LATENT_ENTROPY
bool "Force initialization of variables containing userspace addresses"
- # Currently STRUCTLEAK inserts initialization out of live scope of
- # variables from KASAN point of view. This leads to KASAN false
- # positive reports. Prohibit this combination for now.
- depends on !KASAN_EXTRA
This plugin zero-initializes any structures containing a
__user attribute. This can prevent some classes of information