From: Masami Hiramatsu <mhiramat@kernel.org>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Anton Blanchard <anton@samba.org>,
Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/4] powerpc: build out kprobes blacklist
Date: Thu, 27 Apr 2017 11:24:59 +0900 [thread overview]
Message-ID: <20170427112459.c45b6b1e2d6889c5dadabc3f@kernel.org> (raw)
In-Reply-To: <cover.1493137432.git.naveen.n.rao@linux.vnet.ibm.com>
Hello Naveen,
On Tue, 25 Apr 2017 22:04:05 +0530
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> wrote:
> This is the second in the series of patches to build out an appropriate
> kprobes blacklist. This series blacklists system_call() and functions
> involved when handling the trap itself. Not everything is covered, but
> this is the first set of functions that I have tested with. More
> patches to follow once I expand my tests.
OK, btw, have you tested to put kprobes on these functions and
saw kernel panic happened?
> I have converted many labels into private -- these are labels that I
> felt are not necessary to read stack traces. If any of those are
> important to have, please let me know.
At least from the viewpoint of kprobe-blacklist macros, it seems
good to me :)
Reviewed-by: Masami Hiramatsu <mhiramat@kernel.org>
for this series.
Thank you,
>
> - Naveen
>
> Naveen N. Rao (4):
> powerpc/kprobes: cleanup system_call_common and blacklist it from
> kprobes
> powerpc/kprobes: un-blacklist system_call() from kprobes
> powerpc/kprobes: blacklist functions invoked on a trap
> powerpc/kprobes: blacklist functions involved when returning from
> exception
>
> arch/powerpc/kernel/entry_64.S | 94 +++++++++++++++++++-----------------
> arch/powerpc/kernel/exceptions-64s.S | 1 +
> arch/powerpc/kernel/time.c | 3 ++
> arch/powerpc/kernel/traps.c | 3 ++
> arch/powerpc/platforms/pseries/dtl.c | 2 +
> 5 files changed, 60 insertions(+), 43 deletions(-)
>
> --
> 2.12.1
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2017-04-27 2:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 16:34 [PATCH 0/4] powerpc: build out kprobes blacklist Naveen N. Rao
2017-04-25 16:34 ` [PATCH 1/4] powerpc/kprobes: cleanup system_call_common and blacklist it from kprobes Naveen N. Rao
2017-04-25 16:34 ` [PATCH 2/4] powerpc/kprobes: un-blacklist system_call() " Naveen N. Rao
2017-04-25 16:34 ` [PATCH 3/4] powerpc/kprobes: blacklist functions invoked on a trap Naveen N. Rao
2017-04-25 16:34 ` [PATCH 4/4] powerpc/kprobes: blacklist functions involved when returning from exception Naveen N. Rao
2017-04-27 2:24 ` Masami Hiramatsu [this message]
2017-04-27 6:16 ` [PATCH 0/4] powerpc: build out kprobes blacklist Naveen N. Rao
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=20170427112459.c45b6b1e2d6889c5dadabc3f@kernel.org \
--to=mhiramat@kernel.org \
--cc=ananth@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
/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).