linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/2] powerpc: kprobes: blacklist exception vectors
Date: Wed, 19 Apr 2017 20:59:50 +0530	[thread overview]
Message-ID: <cover.1492614257.git.naveen.n.rao@linux.vnet.ibm.com> (raw)

This is the first of a series of patches to build up a suitable kprobes
blacklist. This series only blacklists the exception vectors.

While I have more patches in the works to blacklist other symbols, I
wanted to get some early feedback on these two patches to ensure that
the approach is ok. So, I'm posting these right away.

I'd especially appreciate a review of the first patch and feedback on
whether it does the right thing with/without relocation. My tests
didn't reveal any issues.


Thanks,
Naveen

Naveen N. Rao (2):
  powerpc: kprobes: blacklist exception handlers
  powerpc: kprobes: blacklist exception common handlers

 arch/powerpc/include/asm/head-64.h  | 1 +
 arch/powerpc/include/asm/sections.h | 1 +
 arch/powerpc/kernel/kprobes.c       | 9 +++++++++
 arch/powerpc/kernel/vmlinux.lds.S   | 2 ++
 4 files changed, 13 insertions(+)

-- 
2.12.1

             reply	other threads:[~2017-04-19 15:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 15:29 Naveen N. Rao [this message]
2017-04-19 15:29 ` [PATCH 1/2] powerpc: kprobes: blacklist exception handlers Naveen N. Rao
2017-04-20  6:33   ` Michael Ellerman
2017-04-20  7:04     ` Naveen N. Rao
2017-04-20 12:30       ` Michael Ellerman
2017-04-23 11:53   ` [1/2] " Michael Ellerman
2017-04-19 15:29 ` [PATCH 2/2] powerpc: kprobes: blacklist exception common handlers Naveen N. Rao
2017-04-23 11:53   ` [2/2] " Michael Ellerman

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.1492614257.git.naveen.n.rao@linux.vnet.ibm.com \
    --to=naveen.n.rao@linux.vnet.ibm.com \
    --cc=ananth@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mhiramat@kernel.org \
    --cc=mpe@ellerman.id.au \
    /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).