From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Kees Cook <keescook@chromium.org>
Cc: Alexander Potapenko <glider@google.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Kostya Serebryany <kcc@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Sandeep Patil <sspatil@android.com>,
Laura Abbott <labbott@redhat.com>,
Randy Dunlap <rdunlap@infradead.org>,
Alexander Popov <alpopov@ptsecurity.com>,
Michal Marek <michal.lkml@markovi.net>,
Emese Revfy <re.emese@gmail.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org,
Kernel Hardening <kernel-hardening@lists.openwall.com>
Subject: Re: [PATCH 0/3] Kconfig: Refactor memory initialization hardening
Date: Thu, 11 Apr 2019 16:59:13 +0900 [thread overview]
Message-ID: <CAK7LNATj3_=4pW6R7ie_EXh_X3U+JNK_6Y6NLT8XjftmezAbFA@mail.gmail.com> (raw)
In-Reply-To: <20190410161612.18545-1-keescook@chromium.org>
On Thu, Apr 11, 2019 at 1:16 AM Kees Cook <keescook@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
>
> 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
>
> --
> 2.17.1
>
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2019-04-11 7:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 16:16 [PATCH 0/3] Kconfig: Refactor memory initialization hardening Kees Cook
2019-04-10 16:16 ` [PATCH 1/3] Kconfig: Create "kernel hardening" config area Kees Cook
2019-04-11 8:50 ` Masahiro Yamada
2019-04-11 16:59 ` Kees Cook
2019-04-10 16:16 ` [PATCH 2/3] kbuild: Move stackleak config to Kconfig.hardening Kees Cook
2019-04-10 16:16 ` [PATCH 3/3] kbuild: Implement Clang's stack initialization Kees Cook
2019-04-11 8:05 ` Masahiro Yamada
2019-04-11 17:07 ` Kees Cook
2019-04-11 7:59 ` Masahiro Yamada [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK7LNATj3_=4pW6R7ie_EXh_X3U+JNK_6Y6NLT8XjftmezAbFA@mail.gmail.com' \
--to=yamada.masahiro@socionext.com \
--cc=alpopov@ptsecurity.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=jmorris@namei.org \
--cc=kcc@google.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=rdunlap@infradead.org \
--cc=re.emese@gmail.com \
--cc=serge@hallyn.com \
--cc=sspatil@android.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).