3 Commits

Author	SHA1	Message	Date
Alexander Potapenko	e0c6791d04	BACKPORT: security: Create "kernel hardening" config area ... Right now kernel hardening options are scattered around various Kconfig files. This can be a central place to collect these kinds of options going forward. This is initially populated with the memory initialization options from the gcc-plugins. The Android backport only moves the config options available in 4.19 at the moment. Change-Id: Iadf83f71da5410bad0aff01309365de0809fde96 Signed-off-by: Kees Cook <keescook@chromium.org> Acked-by: Masahiro Yamada <yamada.masahiro@socionext.com> (cherry picked from commit 9f671e58159adea641f76c56d1f0bbdcb3c524ff) Bug: 133428616 Signed-off-by: Alexander Potapenko <glider@google.com>	2019-06-17 19:26:08 +00:00
Kees Cook	b04413330c	gcc-plugins: Disable when building under Clang ... Prior to doing compiler feature detection in Kconfig, attempts to build GCC plugins with Clang would fail the build, much in the same way missing GCC plugin headers would fail the build. However, now that this logic has been lifted into Kconfig, add an explicit test for GCC (instead of duplicating it in the feature-test script). Reported-by: Stefan Agner <stefan@agner.ch> Signed-off-by: Kees Cook <keescook@chromium.org> Reviewed-by: Masahiro Yamada <yamada.masahiro@socionext.com>	2018-08-23 10:06:12 -07:00
Masahiro Yamada	45332b1bdf	gcc-plugins: split out Kconfig entries to scripts/gcc-plugins/Kconfig ... Collect relevant code into the scripts/gcc-plugins directory. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Kees Cook <keescook@chromium.org>	2018-07-24 16:11:07 -07:00