All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] lkdtm updates for next, part 2
Date: Tue, 15 Aug 2017 12:43:16 -0700	[thread overview]
Message-ID: <20170815194316.GA31327@beast> (raw)

Hi Greg,

Please pull these additional lkdtm changes for next.

Thanks!

-Kees

The following changes since commit c7fea48876773603721f545f8c1a2f894291ef85:

  lkdtm: Provide timing tests for atomic_t vs refcount_t (2017-07-26 14:38:04 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/lkdtm-next-part2

for you to fetch changes up to 93e78c6b14c42abe4018c815aeea2aa491522fae:

  lkdtm: Add -fstack-protector-strong test (2017-08-15 12:27:35 -0700)

----------------------------------------------------------------
- Add new CORRUPT_STACK_STRONG to test -fstack-protector-strong, since
  the existing CORRUPT_STACK test only tested regular -fstack-protector.
- Add pair of tests for checking kernel stack leading/trailing guard pages
  under VMAP_STACK: STACK_GUARD_PAGE_LEADING and STACK_GUARD_PAGE_TRAILING.

----------------------------------------------------------------
Kees Cook (2):
      lkdtm: Test VMAP_STACK allocates leading/trailing guard pages
      lkdtm: Add -fstack-protector-strong test

 drivers/misc/lkdtm.h      |  3 +++
 drivers/misc/lkdtm_bugs.c | 51 ++++++++++++++++++++++++++++++++++++++++++++---
 drivers/misc/lkdtm_core.c |  3 +++
 3 files changed, 54 insertions(+), 3 deletions(-)

-- 
Kees Cook
Pixel Security

             reply	other threads:[~2017-08-15 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 19:43 Kees Cook [this message]
2017-08-16  1:12 ` [GIT PULL] lkdtm updates for next, part 2 Greg Kroah-Hartman

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=20170815194316.GA31327@beast \
    --to=keescook@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.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.