From: Kees Cook <keescook@chromium.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PULL] lkdtm update (next)
Date: Thu, 7 Jul 2016 11:14:35 -0700 [thread overview]
Message-ID: <20160707181435.GA20948@www.outflux.net> (raw)
Hi,
Please pull these lkdtm changes for next.
Thanks!
-Kees
The following changes since commit e2402b1d214e5d50e807773563d590115a161f45:
nvmem: imx-ocotp: Fix assignment warning. (2016-06-25 07:42:55 -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 c479e3fd88703c4b1049d7102a3fa8c6b3affef5:
lkdtm: use struct arrays instead of enums (2016-07-07 11:09:27 -0700)
----------------------------------------------------------------
refactoring for multiple source files and better layout
----------------------------------------------------------------
Kees Cook (12):
lkdtm: add usercopy test for blocking kernel text
lkdtm: drop "alloc_size" parameter
lkdtm: split usercopy tests to separate file
lkdtm: split memory permissions tests to separate file
lkdtm: split heap corruption tests to separate file
lkdtm: split remaining logic bug tests to separate file
lkdtm: remove intentional off-by-one array access
lkdtm: rename "count" to "crash_count"
lkdtm: rename globals for clarity
lkdtm: reorganize module paramaters
lkdtm: move jprobe entry points to start of source
lkdtm: use struct arrays instead of enums
drivers/misc/Makefile | 4 +
drivers/misc/lkdtm.h | 51 ++
drivers/misc/lkdtm_bugs.c | 152 +++++
drivers/misc/lkdtm_core.c | 1246 ++++++++---------------------------------
drivers/misc/lkdtm_heap.c | 146 +++++
drivers/misc/lkdtm_perms.c | 203 +++++++
drivers/misc/lkdtm_usercopy.c | 315 +++++++++++
7 files changed, 1106 insertions(+), 1011 deletions(-)
create mode 100644 drivers/misc/lkdtm_bugs.c
create mode 100644 drivers/misc/lkdtm_heap.c
create mode 100644 drivers/misc/lkdtm_perms.c
create mode 100644 drivers/misc/lkdtm_usercopy.c
--
Kees Cook
Chrome OS & Brillo Security
next reply other threads:[~2016-07-07 18:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 18:14 Kees Cook [this message]
2016-07-12 18:42 ` Kees Cook
2016-07-13 1:00 ` Greg KH
2016-07-13 3:03 ` Kees Cook
2016-07-14 3:00 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2016-07-15 23:16 Kees Cook
2016-07-16 23:30 ` Greg KH
2016-06-10 23:02 Kees Cook
2016-06-11 0:00 ` Greg KH
2016-06-11 0:38 ` Kees Cook
2016-06-11 5:09 ` Greg KH
2016-03-01 22:31 Kees Cook
2016-03-02 0:53 ` Greg KH
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=20160707181435.GA20948@www.outflux.net \
--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
all inboxes | Powered by JetHome®