diff options
author | Nathan Chancellor <nathan@kernel.org> | 2025-04-14 15:00:59 -0700 |
---|---|---|
committer | Kees Cook <kees@kernel.org> | 2025-04-15 13:50:17 -0700 |
commit | cdc2e1d9d929d7f7009b3a5edca52388a2b0891f (patch) | |
tree | 9fac8e5412835320a8ce28fd1c215a4631da74e4 /rust/helpers/task.c | |
parent | f5c68a4e84f9feca3be578199ec648b676db2030 (diff) | |
download | linux-cdc2e1d9d929d7f7009b3a5edca52388a2b0891f.tar.gz linux-cdc2e1d9d929d7f7009b3a5edca52388a2b0891f.tar.bz2 linux-cdc2e1d9d929d7f7009b3a5edca52388a2b0891f.zip |
lib/Kconfig.ubsan: Remove 'default UBSAN' from UBSAN_INTEGER_WRAP
CONFIG_UBSAN_INTEGER_WRAP is 'default UBSAN', which is problematic for a
couple of reasons.
The first is that this sanitizer is under active development on the
compiler side to come up with a solution that is maintainable on the
compiler side and usable on the kernel side. As a result of this, there
are many warnings when the sanitizer is enabled that have no clear path
to resolution yet but users may see them and report them in the meantime.
The second is that this option was renamed from
CONFIG_UBSAN_SIGNED_WRAP, meaning that if a configuration has
CONFIG_UBSAN=y but CONFIG_UBSAN_SIGNED_WRAP=n and it is upgraded via
olddefconfig (common in non-interactive scenarios such as CI),
CONFIG_UBSAN_INTEGER_WRAP will be silently enabled again.
Remove 'default UBSAN' from CONFIG_UBSAN_INTEGER_WRAP until it is ready
for regular usage and testing from a broader community than the folks
actively working on the feature.
Cc: stable@vger.kernel.org
Fixes: 557f8c582a9b ("ubsan: Reintroduce signed overflow sanitizer")
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Link: https://lore.kernel.org/r/20250414-drop-default-ubsan-integer-wrap-v1-1-392522551d6b@kernel.org
Signed-off-by: Kees Cook <kees@kernel.org>
Diffstat (limited to 'rust/helpers/task.c')
0 files changed, 0 insertions, 0 deletions