From: Kees Cook <keescook@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Christophe Leroy <christophe.leroy@c-s.fr>
Subject: [GIT PULL] lkdtm updates for -next
Date: Wed, 9 Jan 2019 12:12:40 -0800 [thread overview]
Message-ID: <20190109201240.GA33464@beast> (raw)
Hi Greg,
Please pull these lkdtm changes for next (into, I assume, your
drivers-misc tree).
Thanks!
-Kees
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
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 59a12205d3c32aee4c13ca36889fdf7cfed31126:
lkdtm: Add tests for NULL pointer dereference (2019-01-09 12:00:31 -0800)
----------------------------------------------------------------
lkdtm updates and new tests
- Check NULL dereferences (Christophe Leroy)
- Print real addresses for debugging (Christophe Leroy)
- Drop CONFIG_BLOCK dependency
----------------------------------------------------------------
Christophe Leroy (2):
lkdtm: Print real addresses
lkdtm: Add tests for NULL pointer dereference
Kees Cook (1):
lkdtm: Do not depend on BLOCK and clean up headers
drivers/misc/lkdtm/core.c | 11 ++---------
drivers/misc/lkdtm/lkdtm.h | 2 ++
drivers/misc/lkdtm/perms.c | 36 +++++++++++++++++++++++++++---------
lib/Kconfig.debug | 1 -
4 files changed, 31 insertions(+), 19 deletions(-)
--
Kees Cook
next reply other threads:[~2019-01-09 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 20:12 Kees Cook [this message]
2019-01-10 7:08 ` [GIT PULL] lkdtm updates for -next Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2022-05-17 21:52 Kees Cook
2022-05-19 15:20 ` Greg Kroah-Hartman
2021-12-17 0:02 Kees Cook
2021-12-17 9:06 ` Greg Kroah-Hartman
2017-10-06 15:31 Kees Cook
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=20190109201240.GA33464@beast \
--to=keescook@chromium.org \
--cc=christophe.leroy@c-s.fr \
--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