Revert "fortify: Allow KUnit test to build without FORTIFY"
authorKees Cook <keescook@chromium.org>
Mon, 3 Jul 2023 19:50:26 +0000 (12:50 -0700)
committerKees Cook <keescook@chromium.org>
Mon, 3 Jul 2023 19:50:26 +0000 (12:50 -0700)
commit5e2956ee46244ffba1d345bae8115aa5dc199adc
treefe3bdba825e5b567adfc4624195ec9c6ba06aed2
parent47f04616f2c9b2f4f0c9127e30ca515a078db591
Revert "fortify: Allow KUnit test to build without FORTIFY"

This reverts commit a9dc8d0442294b426b1ebd4ec6097c82ebe282e0.

The standard for KUnit is to not build tests at all when required
functionality is missing, rather than doing test "skip". Restore this
for the fortify tests, so that architectures without
CONFIG_ARCH_HAS_FORTIFY_SOURCE do not emit unsolvable warnings.

Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Closes: https://lore.kernel.org/all/CAMuHMdUrxOEroHVUt7-mAnKSBjY=a-D3jr+XiAifuwv06Ob9Pw@mail.gmail.com
Signed-off-by: Kees Cook <keescook@chromium.org>
lib/Kconfig.debug
lib/fortify_kunit.c