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
Date: Wed, 2 Aug 2017 11:58:25 -0700	[thread overview]
Message-ID: <20170802185825.GA39980@beast> (raw)

Hi Greg,

Please pull these lkdtm changes into your drivers/misc tree for -next.

Thanks!

-Kees

The following changes since commit 520eccdfe187591a51ea9ab4c1a024ae4d0f68d9:

  Linux 4.13-rc2 (2017-07-23 16:15:17 -0700)

are available in the git repository at:

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

for you to fetch changes up to c7fea48876773603721f545f8c1a2f894291ef85:

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

----------------------------------------------------------------
improvements for refcount protections

----------------------------------------------------------------
Kees Cook (2):
      lkdtm: Provide more complete coverage for REFCOUNT tests
      lkdtm: Provide timing tests for atomic_t vs refcount_t

 drivers/misc/Makefile         |   1 +
 drivers/misc/lkdtm.h          |  27 ++-
 drivers/misc/lkdtm_bugs.c     |  83 ---------
 drivers/misc/lkdtm_core.c     |  25 ++-
 drivers/misc/lkdtm_refcount.c | 400 ++++++++++++++++++++++++++++++++++++++++++
 5 files changed, 441 insertions(+), 95 deletions(-)
 create mode 100644 drivers/misc/lkdtm_refcount.c

-- 
Kees Cook
Pixel Security

             reply	other threads:[~2017-08-02 18:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 18:58 Kees Cook [this message]
2017-08-02 19:42 ` [GIT PULL] lkdtm updates for next 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=20170802185825.GA39980@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.