summaryrefslogtreecommitdiffstats
path: root/lib/Kconfig
diff options
context:
space:
mode:
authorSami Tolvanen <samitolvanen@google.com>2023-06-23 00:11:43 +0000
committerMasahiro Yamada <masahiroy@kernel.org>2023-06-25 23:12:20 +0900
commit25a21fbb934a0d989e1858f83c2ddf4cfb2ebe30 (patch)
tree82277e8c4a4eecad173436a580441a6f1bf0b20f /lib/Kconfig
parentddf56288eebd1fe82c46fc9f693b5b18045cddb6 (diff)
downloadlinux-stable-25a21fbb934a0d989e1858f83c2ddf4cfb2ebe30.tar.gz
linux-stable-25a21fbb934a0d989e1858f83c2ddf4cfb2ebe30.tar.bz2
linux-stable-25a21fbb934a0d989e1858f83c2ddf4cfb2ebe30.zip
kbuild: Disable GCOV for *.mod.o
With GCOV_PROFILE_ALL, Clang injects __llvm_gcov_* functions to each object file, including the *.mod.o. As we filter out CC_FLAGS_CFI for *.mod.o, the compiler won't generate type hashes for the injected functions, and therefore indirectly calling them during module loading trips indirect call checking. Enabling CFI for *.mod.o isn't sufficient to fix this issue after commit 0c3e806ec0f9 ("x86/cfi: Add boot time hash randomization"), as *.mod.o aren't processed by objtool, which means any hashes emitted there won't be randomized. Therefore, in addition to disabling CFI for *.mod.o, also disable GCOV, as the object files don't otherwise contain any executable code. Fixes: cf68fffb66d6 ("add support for Clang CFI") Reported-by: Joe Fradley <joefradley@google.com> Signed-off-by: Sami Tolvanen <samitolvanen@google.com> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org> Reviewed-by: Kees Cook <keescook@chromium.org> Reviewed-by: Nick Desaulniers <ndesaulniers@google.com> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Diffstat (limited to 'lib/Kconfig')
0 files changed, 0 insertions, 0 deletions