[GIT PULL] lkdtm updates for next

[GIT PULL] lkdtm updates for next

[Kees Cook]

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

Re: [GIT PULL] lkdtm updates for next

[Greg Kroah-Hartman]

On Wed, Aug 02, 2017 at 11:58:25AM -0700, Kees Cook wrote:
> 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

That's just about the smallest pull request message ever :(

Please at least provide a bit more info next time.

thanks,

greg k-h