From: Kees Cook <keescook@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: Kees Cook <keescook@chromium.org>,
Emese Revfy <re.emese@gmail.com>,
Alexander Popov <alex.popov@linux.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Laura Abbott <labbott@redhat.com>, Jann Horn <jannh@google.com>,
Alexander Potapenko <glider@google.com>,
kernel-hardening@lists.openwall.com
Subject: [PATCH 0/2] gcc-plugins: structleak: Generalize to all variable types
Date: Tue, 12 Feb 2019 10:04:39 -0800 [thread overview]
Message-ID: <20190212180441.15340-1-keescook@chromium.org> (raw)
Instead of a new plugin for stack initialization[1], this improves
structleak to handle initialization of all variable types. Since the
instrumentation happens at a different point, the "switch" statement
changes from the earlier posting[2] are no longer needed. As before,
this also introduces a stack initialization regression testing module to
validate various kinds of stack variable usage vs compiler instrumentation
for initialization. See the individual patches for more details.
Thanks!
-Kees
[1] https://lkml.kernel.org/r/CA+55aFykZL+cSBJjBBts7ebEFfyGPdMzTmLSxKnT_29=j942dA@mail.gmail.com
[2] https://lkml.kernel.org/r/20190123110349.35882-1-keescook@chromium.org
Kees Cook (2):
gcc-plugins: structleak: Generalize to all variable types
lib: Introduce test_stackinit module
lib/Kconfig.debug | 10 +
lib/Makefile | 1 +
lib/test_stackinit.c | 378 ++++++++++++++++++++++++
scripts/Makefile.gcc-plugins | 2 +
scripts/gcc-plugins/Kconfig | 58 +++-
scripts/gcc-plugins/structleak_plugin.c | 36 ++-
6 files changed, 463 insertions(+), 22 deletions(-)
create mode 100644 lib/test_stackinit.c
--
2.17.1
next reply other threads:[~2019-02-12 18:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 18:04 Kees Cook [this message]
2019-02-12 18:04 ` [PATCH 1/2] gcc-plugins: structleak: Generalize to all variable types Kees Cook
2019-02-28 20:27 ` Arnd Bergmann
2019-03-02 9:04 ` Ard Biesheuvel
2019-03-02 15:43 ` Kees Cook
2019-03-02 22:15 ` Arnd Bergmann
2019-03-04 17:32 ` Kees Cook
2019-03-11 23:05 ` Alexander Popov
2019-03-13 19:01 ` Kees Cook
2019-02-12 18:04 ` [PATCH 2/2] lib: Introduce test_stackinit module Kees Cook
2019-03-11 10:52 ` Geert Uytterhoeven
2019-04-23 22:42 ` Kees Cook
2019-02-15 17:38 ` [PATCH 0/2] gcc-plugins: structleak: Generalize to all variable types Ard Biesheuvel
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=20190212180441.15340-1-keescook@chromium.org \
--to=keescook@chromium.org \
--cc=alex.popov@linux.com \
--cc=ard.biesheuvel@linaro.org \
--cc=glider@google.com \
--cc=jannh@google.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=re.emese@gmail.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).