x86/percpu: Disable named address spaces for UBSAN_BOOL with KASAN for GCC < 14.2
[ Upstream commit b6762467a09ba8838c499e4f36561e82fc608ed1 ] GCC < 14.2 does not correctly propagate address space qualifiers with -fsanitize=bool,enum. Together with address sanitizer then causes that load to be sanitized. Disable named address spaces for GCC < 14.2 when both, UBSAN_BOOL and KASAN are enabled. Reported-by: Matt Fleming <matt@readmodwrite.com> Signed-off-by: Uros Bizjak <ubizjak@gmail.com> Signed-off-by: Ingo Molnar <mingo@kernel.org> Link: https://lore.kernel.org/r/20250227140715.2276353-1-ubizjak@gmail.com Closes: https://lore.kernel.org/lkml/20241213190119.3449103-1-matt@readmodwrite.com/ Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
committed by
Greg Kroah-Hartman
parent
837f5cb7be
commit
640bb22521
@@ -2434,18 +2434,20 @@ config CC_HAS_NAMED_AS
|
||||
def_bool $(success,echo 'int __seg_fs fs; int __seg_gs gs;' | $(CC) -x c - -S -o /dev/null)
|
||||
depends on CC_IS_GCC
|
||||
|
||||
#
|
||||
# -fsanitize=kernel-address (KASAN) and -fsanitize=thread (KCSAN)
|
||||
# are incompatible with named address spaces with GCC < 13.3
|
||||
# (see GCC PR sanitizer/111736 and also PR sanitizer/115172).
|
||||
#
|
||||
|
||||
config CC_HAS_NAMED_AS_FIXED_SANITIZERS
|
||||
def_bool CC_IS_GCC && GCC_VERSION >= 130300
|
||||
def_bool y
|
||||
depends on !(KASAN || KCSAN) || GCC_VERSION >= 130300
|
||||
depends on !(UBSAN_BOOL && KASAN) || GCC_VERSION >= 140200
|
||||
|
||||
config USE_X86_SEG_SUPPORT
|
||||
def_bool y
|
||||
depends on CC_HAS_NAMED_AS
|
||||
#
|
||||
# -fsanitize=kernel-address (KASAN) and -fsanitize=thread
|
||||
# (KCSAN) are incompatible with named address spaces with
|
||||
# GCC < 13.3 - see GCC PR sanitizer/111736.
|
||||
#
|
||||
depends on !(KASAN || KCSAN) || CC_HAS_NAMED_AS_FIXED_SANITIZERS
|
||||
def_bool CC_HAS_NAMED_AS
|
||||
depends on CC_HAS_NAMED_AS_FIXED_SANITIZERS
|
||||
|
||||
config CC_HAS_SLS
|
||||
def_bool $(cc-option,-mharden-sls=all)
|
||||
|
||||
Reference in New Issue
Block a user