This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: kernel panic when kretprobe all system calls

From: Hien Nguyen <hien at us dot ibm dot com>
To: "Frank Ch. Eigler" <fche at elastic dot org>
Cc: systemtap at sources dot redhat dot com, lglyahoo-news at yahoo dot com dot cn
Date: Mon, 26 Sep 2005 08:55:08 -0700
Subject: Re: kernel panic when kretprobe all system calls
References: <20050924194059.GA25059@elastic.org>

Frank Ch. Eigler wrote:

Hi -

[... kretprobes on syscalls ...]


This has been seen before, and is being tracked as bug #1345 in
bugzilla.  It has apparently been reproduced by the kretprobes
developers and is being debugged.  More RAM seems to trigger the
bug less often.

- FChE

It helps if we don't insert return probes in sys_calls such as sys_execve, sys_exit, sys_groupexit. Frank, can we tempory put an retprobe embargo policy on those system calls?

Hien.

Follow-Ups:
- Re: kernel panic when kretprobe all system calls
  - From: Frank Ch. Eigler

References:
- Re: kernel panic when kretprobe all system calls
  - From: Frank Ch. Eigler

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]