All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [GIT PULL] gcc-plugin updates for v5.1-rc1
Date: Mon, 4 Mar 2019 09:48:02 -0800	[thread overview]
Message-ID: <20190304174802.GA6629@beast> (raw)

Hi Linus,

Please pull these gcc-plugin changes for v5.1-rc1. This adds additional
type coverage to the existing structleak plugin and adds a large set of
selftests to help evaluate stack variable zero-initialization coverage
(which can be used to test whatever instrumentation might be performing
zero-initialization: either with the structleak plugin or with Clang's
coming "-ftrivial-auto-var-init=zero" option).

Note that there is a minor conflict seen in linux-next with KASAN changes
in -mm, which removes the !KASAN_EXTRA depends from structleak. sfr's
resolution is correct:
https://lkml.kernel.org/r/20190213170345.656c3030@canb.auug.org.au

Thanks!

-Kees

The following changes since commit 49a57857aeea06ca831043acbb0fa5e0f50602fd:

  Linux 5.0-rc3 (2019-01-21 13:14:44 +1300)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/gcc-plugins-v5.1-rc1

for you to fetch changes up to 50ceaa95ea09703722b30b4afa617c972071cd7f:

  lib: Introduce test_stackinit module (2019-03-04 09:29:52 -0800)

----------------------------------------------------------------
increased structleak coverage

- And scalar and array initialization coverage
- Refactor Kconfig to make options more clear
- Add self-test module for testing automatic initialization

----------------------------------------------------------------
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

-- 
Kees Cook

             reply	other threads:[~2019-03-04 17:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 17:48 Kees Cook [this message]
2019-03-09 19:55 ` [GIT PULL] gcc-plugin updates for v5.1-rc1 pr-tracker-bot

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=20190304174802.GA6629@beast \
    --to=keescook@chromium.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.