[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Wed, 10 Apr 2019 09:16:09 -0700
From: Kees Cook <keescook@...omium.org>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Kees Cook <keescook@...omium.org>,
Alexander Potapenko <glider@...gle.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Kostya Serebryany <kcc@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Sandeep Patil <sspatil@...roid.com>,
Laura Abbott <labbott@...hat.com>,
Randy Dunlap <rdunlap@...radead.org>,
Alexander Popov <alpopov@...ecurity.com>,
Michal Marek <michal.lkml@...kovi.net>,
Emese Revfy <re.emese@...il.com>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org,
kernel-hardening@...ts.openwall.com
Subject: [PATCH 0/3] Kconfig: Refactor memory initialization hardening
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
Kees Cook (3):
Kconfig: Create "kernel hardening" config area
kbuild: Move stackleak config to Kconfig.hardening
kbuild: Implement Clang's stack initialization
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
--
2.17.1
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
