This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: kprobe fault handling
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: prasanna at in dot ibm dot com
- Cc: systemtap at sources dot redhat dot com
- Date: 06 Sep 2005 11:09:13 -0400
- Subject: Re: kprobe fault handling
- References: <20050906182635.GA2700@in.ibm.com>
prasanna wrote:
> [...] yes, in situtations when fault_handler is executed, users can
> either correct the faulty instruction and singlestep again or he can
> just replace back the original instruction, disarm the probe and
> continue. [...]
Is there a modules-accessible kprobes API for disarming a probe on the
fly?
One thing perhaps I didn't make clear is that I am hoping to use the
kprobes fault_handler hook in order to catch problems that occur
*during* the pre_handler execution. In other words, it is meant as
additional protection for bugs in tapsets, the translator, whatnot.
For example, if a probe handler does something crazy and branches to
pc=0, I'd like to unwind/disable the handler, signal the situation,
and let the kernel run along as if the probe wasn't there in the first
place. It looks like this may not be all there now, so I will disable
the new code in the translator code.
- FChE