All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/2] Show kprobe blacklisted address ranges in debugfs
Date: Thu, 29 Jun 2017 19:38:36 +0530	[thread overview]
Message-ID: <cover.1498744665.git.naveen.n.rao@linux.vnet.ibm.com> (raw)

Add the ability to discover all blacklisted address _ranges_ (such as
those with __kprobes annotation, __entry text code, et al) through the
kprobes/blacklist debugfs file. This can then be used by userspace to
accurately detect which addresses can't be probed on.

- Naveen


Naveen N. Rao (2):
  kprobes: Simplify kprobe blacklist management
  kprobes: Allow specifying names for certain blacklisted address ranges

 arch/arm64/kernel/probes/kprobes.c | 31 +++++++++-------
 arch/powerpc/kernel/kprobes.c      | 10 ++---
 arch/x86/kernel/kprobes/core.c     | 10 ++---
 include/linux/kprobes.h            |  3 ++
 kernel/kprobes.c                   | 75 +++++++++++++++++++++++---------------
 5 files changed, 76 insertions(+), 53 deletions(-)

-- 
2.13.1

             reply	other threads:[~2017-06-29 14:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29 14:08 Naveen N. Rao [this message]
2017-06-29 14:08 ` [RFC PATCH 1/2] kprobes: Simplify kprobe blacklist management Naveen N. Rao
2017-07-03  3:22   ` Masami Hiramatsu
2017-06-29 14:08 ` [RFC PATCH 2/2] kprobes: Allow specifying names for certain blacklisted address ranges Naveen N. Rao
2017-07-03  3:22   ` Masami Hiramatsu

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=cover.1498744665.git.naveen.n.rao@linux.vnet.ibm.com \
    --to=naveen.n.rao@linux.vnet.ibm.com \
    --cc=ananth@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@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.