From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11681 invoked by alias); 4 Apr 2008 11:19:23 -0000 Received: (qmail 11551 invoked by uid 48); 4 Apr 2008 11:18:40 -0000 Date: Fri, 04 Apr 2008 11:46:00 -0000 Message-ID: <20080404111840.11550.qmail@sourceware.org> From: "fche at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20080404085514.6030.ananth@in.ibm.com> References: <20080404085514.6030.ananth@in.ibm.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug runtime/6030] stap, staprun, stapio interaction quirks: stale module left unloaded X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2008-q2/txt/msg00023.txt.bz2 ------- Additional Comments From fche at redhat dot com 2008-04-04 11:18 ------- We cannot reasonably recover from a kill -9 on staprun. That is the only privileged process that can unload the module. It may have been hand-started, leaving none of our code available to watch over it and restart it. Teaching stap to re-fork staprun another time is perhaps possible, but in your "kill -9 stap staprun" scenario, that wouldn't help either. Note when the module detects its user-space partner process going away, it carries out shutdown as far as it can: deregisters probes, frees memory. A module cannot unload itself AFAIK. So while it is an orphan, it merely sits in memory, and probably blocks a repeat invocation. It's not that bad. Perhaps it's time to reconsider including a script such as http://sourceware.org/ml/systemtap/2008-q1/msg00051.html in the distribution. Or a cron-driven systemtap module cleaner/unloader. -- http://sourceware.org/bugzilla/show_bug.cgi?id=6030 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.