The patch titled
Subject: ubsan-run-time-undefined-behavior-sanity-checker-fix-2
has been removed from the -mm tree. Its filename was
ubsan-run-time-undefined-behavior-sanity-checker-fix-2.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-2
In GCC internals __ubsan_handle_builtin_unreachable() declared
with "noreturn" attribute. Make it noreturn in-kernel too.
Since we can't return from such function call panic() instead.
Signed-off-by: Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
lib/ubsan.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff -puN lib/ubsan.c~ubsan-run-time-undefined-behavior-sanity-checker-fix-2 lib/ubsan.c
--- a/lib/ubsan.c~ubsan-run-time-undefined-behavior-sanity-checker-fix-2
+++ a/lib/ubsan.c
@@ -422,16 +422,16 @@ void __ubsan_handle_shift_out_of_bounds(
}
EXPORT_SYMBOL(__ubsan_handle_shift_out_of_bounds);
-void __ubsan_handle_builtin_unreachable(struct unreachable_data *data)
+
+void __noreturn
+__ubsan_handle_builtin_unreachable(struct unreachable_data *data)
{
unsigned long flags;
- if (suppress_report(&data->location))
- return;
-
ubsan_prologue(&data->location, &flags);
pr_err("calling __builtin_unreachable()\n");
ubsan_epilogue(&flags);
+ panic("can't return from __builtin_unreachable()");
}
EXPORT_SYMBOL(__ubsan_handle_builtin_unreachable);
_
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
ubsan-run-time-undefined-behavior-sanity-checker-fix-4.patch
ubsan-run-time-undefined-behavior-sanity-checker-fix-5.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
