[PATCH 0/3] Kconfig: Refactor memory initialization hardening
yamada.masahiro at socionext.com
Thu Apr 11 07:59:13 UTC 2019
On Thu, Apr 11, 2019 at 1:16 AM Kees Cook <keescook at chromium.org> wrote:
> This is a proposed alternative for the memory initialization series,
> which refactoring the existing gcc plugins into a separate Kconfig
> file and collects all the related options together with some more
> language to describe their differences. The last patch adds the
> Clang auto init option, as done by Alexander Potapenko.
> Since there isn't really a good way to "select" with dependencies,
> I've left out CONFIG_INIT_ALL_MEMORY for the moment...
> Kees Cook (3):
> Kconfig: Create "kernel hardening" config area
I want to see "kconfig:" prefix in the subject line
only for changed in scripts/kconfig/.
> kbuild: Move stackleak config to Kconfig.hardening
This is not a change in the build system.
> kbuild: Implement Clang's stack initialization
I think "gcc-plugin:", "security:' or something is better for the
patch subjects, and this patch series is out of
my maintenance area.
> Makefile | 5 ++
> scripts/gcc-plugins/Kconfig | 121 +-------------------------
> security/Kconfig | 2 +
> security/Kconfig.hardening | 165 ++++++++++++++++++++++++++++++++++++
> 4 files changed, 175 insertions(+), 118 deletions(-)
> create mode 100644 security/Kconfig.hardening
More information about the Linux-security-module-archive