2019-05-19 20:07:45 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2016-01-21 07:00:55 +08:00
|
|
|
config ARCH_HAS_UBSAN_SANITIZE_ALL
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config UBSAN
|
|
|
|
|
bool "Undefined behaviour sanity checker"
|
|
|
|
|
help
|
2020-04-07 11:12:27 +08:00
|
|
|
This option enables the Undefined Behaviour sanity checker.
|
2016-01-21 07:00:55 +08:00
|
|
|
Compile-time instrumentation is used to detect various undefined
|
2020-04-07 11:12:27 +08:00
|
|
|
behaviours at runtime. For more details, see:
|
|
|
|
|
Documentation/dev-tools/ubsan.rst
|
|
|
|
|
|
|
|
|
|
config UBSAN_TRAP
|
|
|
|
|
bool "On Sanitizer warnings, abort the running kernel code"
|
|
|
|
|
depends on UBSAN
|
|
|
|
|
depends on $(cc-option, -fsanitize-undefined-trap-on-error)
|
|
|
|
|
help
|
|
|
|
|
Building kernels with Sanitizer features enabled tends to grow
|
|
|
|
|
the kernel size by around 5%, due to adding all the debugging
|
|
|
|
|
text on failure paths. To avoid this, Sanitizer instrumentation
|
|
|
|
|
can just issue a trap. This reduces the kernel size overhead but
|
|
|
|
|
turns all warnings (including potentially harmless conditions)
|
|
|
|
|
into full exceptions that abort the running kernel code
|
|
|
|
|
(regardless of context, locks held, etc), which may destabilize
|
|
|
|
|
the system. For some system builders this is an acceptable
|
|
|
|
|
trade-off.
|
2016-01-21 07:00:55 +08:00
|
|
|
|
|
|
|
|
config UBSAN_SANITIZE_ALL
|
|
|
|
|
bool "Enable instrumentation for the entire kernel"
|
|
|
|
|
depends on UBSAN
|
|
|
|
|
depends on ARCH_HAS_UBSAN_SANITIZE_ALL
|
2016-03-23 05:27:45 +08:00
|
|
|
|
|
|
|
|
# We build with -Wno-maybe-uninitilzed, but we still want to
|
|
|
|
|
# use -Wmaybe-uninitilized in allmodconfig builds.
|
|
|
|
|
# So dependsy bellow used to disable this option in allmodconfig
|
|
|
|
|
depends on !COMPILE_TEST
|
2016-01-21 07:00:55 +08:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This option activates instrumentation for the entire kernel.
|
|
|
|
|
If you don't enable this option, you have to explicitly specify
|
|
|
|
|
UBSAN_SANITIZE := y for the files/directories you want to check for UB.
|
2016-02-12 08:12:55 +08:00
|
|
|
Enabling this option will get kernel image size increased
|
|
|
|
|
significantly.
|
2016-01-21 07:00:55 +08:00
|
|
|
|
2019-03-08 08:30:16 +08:00
|
|
|
config UBSAN_NO_ALIGNMENT
|
|
|
|
|
bool "Disable checking of pointers alignment"
|
2016-01-21 07:00:55 +08:00
|
|
|
depends on UBSAN
|
2019-03-08 08:30:16 +08:00
|
|
|
default y if HAVE_EFFICIENT_UNALIGNED_ACCESS
|
2016-01-21 07:00:55 +08:00
|
|
|
help
|
2019-03-08 08:30:16 +08:00
|
|
|
This option disables the check of unaligned memory accesses.
|
|
|
|
|
This option should be used when building allmodconfig.
|
|
|
|
|
Disabling this option on architectures that support unaligned
|
2016-01-21 07:00:55 +08:00
|
|
|
accesses may produce a lot of false positives.
|
2016-09-12 20:37:19 +08:00
|
|
|
|
2019-03-08 08:30:16 +08:00
|
|
|
config UBSAN_ALIGNMENT
|
|
|
|
|
def_bool !UBSAN_NO_ALIGNMENT
|
|
|
|
|
|
2018-04-11 07:32:58 +08:00
|
|
|
config TEST_UBSAN
|
|
|
|
|
tristate "Module for testing for undefined behavior detection"
|
|
|
|
|
depends on m && UBSAN
|
|
|
|
|
help
|
|
|
|
|
This is a test module for UBSAN.
|
|
|
|
|
It triggers various undefined behavior, and detect it.
|
