OSDN Git Service

fortify: Explicitly disable Clang support
authorKees Cook <keescook@chromium.org>
Thu, 13 May 2021 04:51:10 +0000 (21:51 -0700)
committerKees Cook <keescook@chromium.org>
Sat, 25 Sep 2021 15:20:49 +0000 (08:20 -0700)
commita52f8a59aef46b59753e583bf4b28fccb069ce64
tree2cd6a83cc7f41e74ed046f927e3944dae5a37e1f
parentc430f60036af44079170ff71a461b9d7cf5ee431
fortify: Explicitly disable Clang support

Clang has never correctly compiled the FORTIFY_SOURCE defenses due to
a couple bugs:

Eliding inlines with matching __builtin_* names
https://bugs.llvm.org/show_bug.cgi?id=50322

Incorrect __builtin_constant_p() of some globals
https://bugs.llvm.org/show_bug.cgi?id=41459

In the process of making improvements to the FORTIFY_SOURCE defenses, the
first (silent) bug (coincidentally) becomes worked around, but exposes
the latter which breaks the build. As such, Clang must not be used with
CONFIG_FORTIFY_SOURCE until at least latter bug is fixed (in Clang 13),
and the fortify routines have been rearranged.

Update the Kconfig to reflect the reality of the current situation.

Signed-off-by: Kees Cook <keescook@chromium.org>
Acked-by: Nick Desaulniers <ndesaulniers@google.com>
Link: https://lore.kernel.org/lkml/CAKwvOd=A+ueGV2ihdy5GtgR2fQbcXjjAtVxv3=cPjffpebZB7A@mail.gmail.com
security/Kconfig