The patch titled
Subject: ubsan-run-time-undefined-behavior-sanity-checker-fix-5
has been removed from the -mm tree. Its filename was
ubsan-run-time-undefined-behavior-sanity-checker-fix-5.patch
This patch was dropped because it was folded into ubsan-run-time-undefined-behavior-sanity-checker.patch
------------------------------------------------------
From: Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx>
Subject: ubsan-run-time-undefined-behavior-sanity-checker-fix-5
Don't use 'bounds-strict' checker. It's a new checker that showed up
in GCC 6. It appeared to cause a lot of false positives in dynamically
allocated structs which has array as the last field, e.g:
[ 72.707515] UBSAN: Undefined behaviour in kernel/pid.c:506:23
[ 72.707517] index 2 is out of range for type 'upid [1]'
Anyway, we have KASAN for these kind of bugs, so we won't lose much by
disabling bounds-strict.
Signed-off-by: Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
scripts/Makefile.ubsan | 1 -
1 file changed, 1 deletion(-)
diff -puN scripts/Makefile.ubsan~ubsan-run-time-undefined-behavior-sanity-checker-fix-5 scripts/Makefile.ubsan
--- a/scripts/Makefile.ubsan~ubsan-run-time-undefined-behavior-sanity-checker-fix-5
+++ a/scripts/Makefile.ubsan
@@ -6,7 +6,6 @@ ifdef CONFIG_UBSAN
CFLAGS_UBSAN += $(call cc-option, -fsanitize=null)
CFLAGS_UBSAN += $(call cc-option, -fsanitize=signed-integer-overflow)
CFLAGS_UBSAN += $(call cc-option, -fsanitize=bounds)
- CFLAGS_UBSAN += $(call cc-option, -fsanitize=bounds-strict)
CFLAGS_UBSAN += $(call cc-option, -fsanitize=object-size)
CFLAGS_UBSAN += $(call cc-option, -fsanitize=returns-nonnull-attribute)
CFLAGS_UBSAN += $(call cc-option, -fsanitize=bool)
_
Patches currently in -mm which might be from aryabinin@xxxxxxxxxxxxx are
kernel-printk-specify-alignment-for-struct-printk_log.patch
mac80211-prevent-build-failure-with-config_ubsan=y.patch
ubsan-run-time-undefined-behavior-sanity-checker.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
