From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5365 invoked by alias); 17 Jul 2008 17:48:07 -0000 Received: (qmail 5355 invoked by uid 22791); 17 Jul 2008 17:48:06 -0000 X-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_47,KAM_MX,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 17 Jul 2008 17:47:49 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m6HHllsQ016255; Thu, 17 Jul 2008 13:47:47 -0400 Received: from pobox-3.corp.redhat.com (pobox-3.corp.redhat.com [10.11.255.67]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6HHlkbC027353; Thu, 17 Jul 2008 13:47:46 -0400 Received: from touchme.toronto.redhat.com (IDENT:postfix@touchme.yyz.redhat.com [10.15.16.9]) by pobox-3.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6HHlLkV026323; Thu, 17 Jul 2008 13:47:46 -0400 Received: from ton.toronto.redhat.com (ton.yyz.redhat.com [10.15.16.15]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 55F158001FF; Thu, 17 Jul 2008 13:47:05 -0400 (EDT) Received: from ton.toronto.redhat.com (localhost.localdomain [127.0.0.1]) by ton.toronto.redhat.com (8.13.1/8.13.1) with ESMTP id m6HHkmOu019490; Thu, 17 Jul 2008 13:46:48 -0400 Received: (from fche@localhost) by ton.toronto.redhat.com (8.13.1/8.13.1/Submit) id m6HHkke5019489; Thu, 17 Jul 2008 13:46:46 -0400 X-Authentication-Warning: ton.toronto.redhat.com: fche set sender to fche@redhat.com using -f To: anithra Cc: systemtap Subject: Re: [Bug runtime/6030] stap, staprun, stapio interaction quirks: stale module left unloaded References: <20080404085514.6030.ananth@in.ibm.com> <20080710170428.32479.qmail@sourceware.org> <487F33EE.9050809@linux.vnet.ibm.com> From: fche@redhat.com (Frank Ch. Eigler) Date: Thu, 17 Jul 2008 17:48:00 -0000 In-Reply-To: <487F33EE.9050809@linux.vnet.ibm.com> (anithra@linux.vnet.ibm.com's message of "Thu, 17 Jul 2008 17:28:38 +0530") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Scanned-By: MIMEDefang 2.58 on 172.16.52.254 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-q3/txt/msg00224.txt.bz2 anithra writes: > [...] kill(SIGTERM, -stap_pid) solves the problem from the StapGUI > point of qview. I'm able to terminate both the stap& stapio process > and thereby unload the module. Good. > But the behaviour of the stap process still doesn't seem correct. If > a signal is sent to the stap process it terminates leaving stapio > running as a zombie and the module still loaded. I still don't quite see how this scenario would happen. If stapio is a zombie, then this means that it has exited. As a part of exiting, stapio attempts to exec "staprun -d MODULE" to unload the module. If a module is left behind loaded, something other than stap process's own signal processing must have been involved. (By the way, there is no such thing as "running as a zombie". Zombie processes are unsightly but otherwise consume essentially no resources.) - FChE