tracing/kprobes: Dump the culprit kprobe in case of kprobe recursion
authorFrederic Weisbecker <fweisbec@gmail.com>
Wed, 26 Aug 2009 21:38:30 +0000 (23:38 +0200)
committerFrederic Weisbecker <fweisbec@gmail.com>
Thu, 27 Aug 2009 00:33:03 +0000 (02:33 +0200)
commit24851d2447830e6cba4c4b641cb73e713f312373
treeb0aa315fc67b3aedab3bd84ef99ea3d933fd365c
parent30a7e073b590ebd1829a906164b0a637e77cc967
tracing/kprobes: Dump the culprit kprobe in case of kprobe recursion

Kprobes can enter into a probing recursion, ie: a kprobe that does an
endless loop because one of its core mechanism function used during
probing is also probed itself.

This patch helps pinpointing the kprobe that raised such recursion
by dumping it and raising a BUG instead of a warning (we also disarm
the kprobe to try avoiding recursion in BUG itself). Having a BUG
instead of a warning stops the stacktrace in the right place and
doesn't pollute the logs with hundreds of traces that eventually end
up in a stack overflow.

Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Masami Hiramatsu <mhiramat@redhat.com>
Cc: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
arch/x86/kernel/kprobes.c
include/linux/kprobes.h
kernel/kprobes.c
This page took 0.040254 seconds and 5 git commands to generate.