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, Arnd Bergmann <arnd@arndb.de>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Dan Li <ashimida@linux.alibaba.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiasheng Jiang <jiasheng@iscas.ac.cn>,
	Kees Cook <keescook@chromium.org>,
	linux-kselftest@vger.kernel.org,
	Muhammad Usama Anjum <usama.anjum@collabora.com>,
	Shuah Khan <shuah@kernel.org>
Subject: [GIT PULL drivers/misc] lkdtm updates for next
Date: Sat, 16 Apr 2022 14:20:54 -0700	[thread overview]
Message-ID: <202204161420.168B8DDBE@keescook> (raw)

Hi Greg,

Please pull these lkdtm updates for -next.

Thanks!

-Kees

The following changes since commit ce522ba9ef7e2d9fb22a39eb3371c0c64e2a433e:

  Linux 5.18-rc2 (2022-04-10 14:21:36 -1000)

are available in the Git repository at:

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

for you to fetch changes up to 2e53b877dc1258d4ac3de98f496bb88ec3bf5e25:

  lkdtm: Add CFI_BACKWARD to test ROP mitigations (2022-04-16 13:57:23 -0700)

----------------------------------------------------------------
lkdtm updates for next

Christophe Leroy (1):
      lkdtm/bugs: Don't expect thread termination without CONFIG_UBSAN_TRAP

Jiasheng Jiang (1):
      lkdtm/bugs: Check for the NULL pointer after calling kmalloc

Kees Cook (4):
      lkdtm/heap: Note conditions for SLAB_LINEAR_OVERFLOW
      lkdtm/usercopy: Expand size of "out of frame" object
      lkdtm: Move crashtype definitions into each category
      lkdtm: Add CFI_BACKWARD to test ROP mitigations

----------------------------------------------------------------

 drivers/misc/lkdtm/bugs.c               |  96 +++++++++++++++------
 drivers/misc/lkdtm/cfi.c                | 145 +++++++++++++++++++++++++++++++-
 drivers/misc/lkdtm/core.c               | 138 +++++++-----------------------
 drivers/misc/lkdtm/fortify.c            |  17 +++-
 drivers/misc/lkdtm/heap.c               |  47 ++++++++---
 drivers/misc/lkdtm/lkdtm.h              | 142 ++++++++-----------------------
 drivers/misc/lkdtm/perms.c              |  47 ++++++++---
 drivers/misc/lkdtm/powerpc.c            |  11 ++-
 drivers/misc/lkdtm/refcount.c           |  65 +++++++++-----
 drivers/misc/lkdtm/stackleak.c          |  11 ++-
 drivers/misc/lkdtm/usercopy.c           |  49 ++++++++---
 tools/testing/selftests/lkdtm/config    |   2 +
 tools/testing/selftests/lkdtm/tests.txt |   1 +
 13 files changed, 471 insertions(+), 300 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2022-04-16 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-16 21:20 Kees Cook [this message]
2022-04-22 13:52 ` [GIT PULL drivers/misc] lkdtm updates for next Greg Kroah-Hartman
  -- strict thread matches above, loose matches on Subject: below --
2019-08-25 22:23 Kees Cook
2019-08-28 20:39 ` 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=202204161420.168B8DDBE@keescook \
    --to=keescook@chromium.org \
    --cc=arnd@arndb.de \
    --cc=ashimida@linux.alibaba.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=dan.carpenter@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jiasheng@iscas.ac.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=usama.anjum@collabora.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 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.