FAILED: Patch "kcsan, compiler_types: avoid duplicate type issues in BPF Type Format" failed to apply to 6.12-stable tree
Sasha Levin
maintainerThe patch below does not apply to the 6.12-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
Thanks,
Sasha
------------------ original commit in Linus's tree ------------------
From 9dc052234da736f7749f19ab6936342ec7dbe3ac Mon Sep 17 00:00:00 2001
From: Alan Maguire <[email protected]>
Date: Fri, 16 Jan 2026 09:17:30 +0000
Subject: [PATCH] kcsan, compiler_types: avoid duplicate type issues in BPF
Type Format
Enabling KCSAN is causing a large number of duplicate types in BTF for core kernel structs like task_struct [1]. This is due to the definition in include/linux/compiler_types.h
`#ifdef __SANITIZE_THREAD__
...
`#define __data_racy volatile
..
`#else
...
`#define __data_racy
...
`#endif
Because some objects in the kernel are compiled without KCSAN flags (KCSAN_SANITIZE) we sometimes get the empty __data_racy annotation for objects; as a result we get multiple conflicting representations of the associated structs in DWARF, and these lead to multiple instances of core kernel types in BTF since they cannot be deduplicated due to the additional modifier in some instances.
Moving the __data_racy definition under CONFIG_KCSAN avoids this problem, since the volatile modifier will be present for both KCSAN and KCSAN_SANITIZE objects in a CONFIG_KCSAN=y kernel.
--- include/linux/compiler_types.h | 23 ++++++++++++++++------- 1 file changed, 16 insertions(+), 7 deletions(-)
include/linux/compiler_types.h +16 -7
@@ -303,6 +303,22 @@ struct ftrace_likely_data {# define __no_kasan_or_inline __always_inline#endif +#ifdef CONFIG_KCSAN +/* +* Type qualifier to mark variables where all data-racy accesses should be +* ignored by KCSAN. Note, the implementation simply marks these variables as +* volatile, since KCSAN will treat such accesses as "marked". +* +* Defined here because defining __data_racy as volatile for KCSAN objects only +* causes problems in BPF Type Format (BTF) generation since struct members +* of core kernel data structs will be volatile in some objects and not in +* others. Instead define it globally for KCSAN kernels. +*/ +# define __data_racy volatile +#else +# define __data_racy +#endif +#ifdef __SANITIZE_THREAD__/* * Clang still emits instrumentation for __tsan_func_{entry,exit}() and builtin
@@ -314,16 +330,9 @@ struct ftrace_likely_data {* disable all instrumentation. See Kconfig.kcsan where this is mandatory. */ # define __no_kcsan __no_sanitize_thread __disable_sanitizer_instrumentation -/* -* Type qualifier to mark variables where all data-racy accesses should be -* ignored by KCSAN. Note, the implementation simply marks these variables as -* volatile, since KCSAN will treat such accesses as "marked". -*/ -# define __data_racy volatile# define __no_sanitize_or_inline __no_kcsan notrace __maybe_unused#else # define __no_kcsan -# define __data_racy#endif #ifdef __SANITIZE_MEMORY__
Signature · 1 line
2.51.0