Hello Naveen, On Tue, 25 Apr 2017 22:04:05 +0530 "Naveen N. Rao" <naveen.n....@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 <mhira...@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 <mhira...@kernel.org>