From: Kees Cook <keescook@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] lkdtm fixes for next
Date: Thu, 9 May 2019 10:19:39 -0700 [thread overview]
Message-ID: <201905091017.DA22A3E0C@keescook> (raw)
Hi Greg,
Please pull these lkdtm fixes for next. If possible, it'd be nice to get
these into v5.2 (they're small fixes), but I'm fine if they have to wait.
I meant to send these earlier, but got distracted by other things.
Thanks!
-Kees
The following changes since commit 8c2ffd9174779014c3fe1f96d9dc3641d9175f00:
Linux 5.1-rc2 (2019-03-24 14:02:26 -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 24cccab42c4199c6daa0a6981e6f6a1ffb0b5a09:
lkdtm/bugs: Adjust recursion test to avoid elision (2019-04-07 10:38:31 -0700)
----------------------------------------------------------------
lkdtm: various fixes
- Move KERNEL_DS test to non-canonical range
- Make stack exhaustion test more robust
----------------------------------------------------------------
Kees Cook (2):
lkdtm/usercopy: Moves the KERNEL_DS test to non-canonical
lkdtm/bugs: Adjust recursion test to avoid elision
drivers/misc/lkdtm/bugs.c | 23 +++++++++++++++++------
drivers/misc/lkdtm/core.c | 6 +++---
drivers/misc/lkdtm/lkdtm.h | 2 +-
drivers/misc/lkdtm/usercopy.c | 10 ++++++----
4 files changed, 27 insertions(+), 14 deletions(-)
--
Kees Cook
next reply other threads:[~2019-05-09 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 17:19 Kees Cook [this message]
2019-05-09 17:26 ` [GIT PULL] lkdtm fixes for next Greg Kroah-Hartman
2019-05-24 18:30 ` 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=201905091017.DA22A3E0C@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;
as well as URLs for NNTP newsgroup(s).