summaryrefslogtreecommitdiff
path: root/lib
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2024-09-17 13:17:27 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2024-09-17 13:17:27 +0200
commitdea435d397ab90d8e682e4162a5b9835d24b1e3a (patch)
tree4d39ab076a3fbc09709b170db8ac6439b4fa4293 /lib
parent61d1ea914b3556c44f9ca04277ab990a60afb44d (diff)
parent7424fc6b86c8980a87169e005f5cd4438d18efe6 (diff)
Merge tag 'x86-core-2024-09-17' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull x86 core update from Thomas Gleixner: "Enable UBSAN traps for x86, which provides better reporting through metadata encodeded into UD1" * tag 'x86-core-2024-09-17' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: x86/traps: Enable UBSAN traps on x86
Diffstat (limited to 'lib')
-rw-r--r--lib/Kconfig.ubsan4
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/Kconfig.ubsan b/lib/Kconfig.ubsan
index bdda600f8dfb..1d4aa7a83b3a 100644
--- a/lib/Kconfig.ubsan
+++ b/lib/Kconfig.ubsan
@@ -29,8 +29,8 @@ config UBSAN_TRAP
Also note that selecting Y will cause your kernel to Oops
with an "illegal instruction" error with no further details
- when a UBSAN violation occurs. (Except on arm64, which will
- report which Sanitizer failed.) This may make it hard to
+ when a UBSAN violation occurs. (Except on arm64 and x86, which
+ will report which Sanitizer failed.) This may make it hard to
determine whether an Oops was caused by UBSAN or to figure
out the details of a UBSAN violation. It makes the kernel log
output less useful for bug reports.