All of lore.kernel.org
 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>
Subject: [GIT PULL] lkdtm updates for -next
Date: Fri, 6 Oct 2017 08:31:29 -0700	[thread overview]
Message-ID: <20171006153129.GA108423@beast> (raw)

Hi,

Please pull these couple lkdtm changes for -next.

Thanks!

-Kees

The following changes since commit e19b205be43d11bff638cad4487008c48d21c103:

  Linux 4.14-rc2 (2017-09-24 16:38:56 -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 ada7bc9b897124dc2c3a45f9896a48b3eb571f11:

  lkdtm: Constify the crashtypes table (2017-10-06 08:12:43 -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 | 164 +++++++++++++---------------------------------
 1 file changed, 47 insertions(+), 117 deletions(-)

-- 
Kees Cook
Pixel Security

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06 15:31 Kees Cook [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-09 20:12 [GIT PULL] lkdtm updates for -next Kees Cook
2019-01-10  7:08 ` Greg Kroah-Hartman
2021-12-17  0:02 Kees Cook
2021-12-17  9:06 ` Greg Kroah-Hartman
2022-05-17 21:52 Kees Cook
2022-05-19 15:20 ` 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=20171006153129.GA108423@beast \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.