From: Kees Cook <keescook@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>
Subject: [GIT PULL drivers/misc] lkdtm updates for next
Date: Sun, 25 Aug 2019 15:23:04 -0700 [thread overview]
Message-ID: <201908251522.DEAF618@keescook> (raw)
Hi Greg,
Please pull these LKDTM updates for next.
Thanks!
-Kees
The following changes since commit 609488bc979f99f805f34e9a32c1e3b71179d10b:
Linux 5.3-rc2 (2019-07-28 12:47:02 -0700)
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 1ee170ea3f0dcf3a4b34f7e7c36559e84bb0d3d6:
lkdtm: Split WARNING into separate tests (2019-08-19 11:13:21 -0700)
----------------------------------------------------------------
Updates to LKDTM for -next
- split WARNING into two tests: with message and without
- add prototype-granularity forward CFI test
----------------------------------------------------------------
Kees Cook (2):
lkdtm: Add Control Flow Integrity test
lkdtm: Split WARNING into separate tests
drivers/misc/lkdtm/Makefile | 1 +
drivers/misc/lkdtm/bugs.c | 7 ++++++-
drivers/misc/lkdtm/cfi.c | 42 ++++++++++++++++++++++++++++++++++++++++++
drivers/misc/lkdtm/core.c | 2 ++
drivers/misc/lkdtm/lkdtm.h | 4 ++++
5 files changed, 55 insertions(+), 1 deletion(-)
create mode 100644 drivers/misc/lkdtm/cfi.c
--
Kees Cook
next reply other threads:[~2019-08-28 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 22:23 Kees Cook [this message]
2019-08-28 20:39 ` [GIT PULL drivers/misc] lkdtm updates for next Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2022-04-16 21:20 Kees Cook
2022-04-22 13:52 ` 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=201908251522.DEAF618@keescook \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox