linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
	Masami Hiramatsu <mhiramat@kernel.org>
Subject: [GIT PULL] lkdtm updates for -next (take 2)
Date: Fri, 6 Oct 2017 13:20:47 -0700	[thread overview]
Message-ID: <20171006202047.GA110637@beast> (raw)


Hi,

Please pull these couple lkdtm changes for -next. This includes fixes for
issues 0-day noticed, for which I've updated my test environment to cover
in the future. (This is also based on -rc3 because arm64 builds are broken
in -rc2.)

Thanks!

-Kees

The following changes since commit 9e66317d3c92ddaab330c125dfe9d06eee268aff:

  Linux 4.14-rc3 (2017-10-01 14:54:54 -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 0f743ba9160f320513450a83c670bc70c695db0a:

  lkdtm: Constify the crashtypes table (2017-10-06 12:53:19 -0700)

----------------------------------------------------------------
- Replace jprobes usage with kprobes
- Constify crashtypes table, add missing static markings

----------------------------------------------------------------
Kees Cook (2):
      lkdtm: Convert from jprobe to kprobe
      lkdtm: Constify the crashtypes table

 drivers/misc/lkdtm_core.c | 172 +++++++++++++++-------------------------------
 1 file changed, 54 insertions(+), 118 deletions(-)

-- 
Kees Cook
Pixel Security

                 reply	other threads:[~2017-10-06 20:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20171006202047.GA110637@beast \
    --to=keescook@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@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).