This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: kernel panic when kretprobe all system calls
- From: "Frank Ch. Eigler" <fche at elastic dot org>
- To: Hien Nguyen <hien at us dot ibm dot com>
- Cc: systemtap at sources dot redhat dot com
- Date: Mon, 26 Sep 2005 12:03:14 -0400
- Subject: Re: kernel panic when kretprobe all system calls
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws;s=default; d=elastic.org;b=MWNKYSDUr2tT8sei9/zX9IPxJ1lrIOJ3+4i5nRUtpzapmaJJRGdcsVs/L5Ifw9Xb5m3M2Q8IxxMtO86Mdijw33W0jX9dXjZg3C3EmssFntQSaMjqRirFCDzpM7FpaaNT;
- References: <20050924194059.GA25059@elastic.org> <433819DC.9020708@us.ibm.com>
Hi -
On Mon, Sep 26, 2005 at 08:55:08AM -0700, Hien Nguyen wrote:
> [...]
> It helps if we don't insert return probes in sys_calls such as
> sys_execve, sys_exit, sys_groupexit.
Does that solve the problem completely? We would need to treat
similarly some of their subsidiary "noreturn" functions.
> Frank, can we tempory put an retprobe embargo policy on those system
> calls?
By policy, you mean code that blacklists certain functions from
probing? I was holding off until results from jkenisto's bug #1235
were collected.
- FChE