From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26053 invoked by alias); 17 Sep 2007 19:15:33 -0000 Received: (qmail 26016 invoked by uid 48); 17 Sep 2007 19:15:22 -0000 Date: Mon, 17 Sep 2007 20:18:00 -0000 From: "mmlnx at us dot ibm dot com" To: systemtap@sources.redhat.com Message-ID: <20070917191522.5042.mmlnx@us.ibm.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug runtime/5042] New: procfs probe script not recreating /proc entries in some cases 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: 2007-q3/txt/msg00618.txt.bz2 I just tried out the new procfs probe feature (very cool, BTW) and found a bug. The bug can be reproduced as follows: 1. Run a procfs probe script that inserts an entry in /proc (e.g., /proc/systemtap/stap_d116efa3785a073ecd3b45ae46950a46_72240/foo). 2. CD to /proc/systemtap/stap_d116efa3785a073ecd3b45ae46950a46_72240 in another xterm. 3. Ctrl-c out of the probe script. You'll see messages like the following in /var/log/messages: Sep 17 11:51:20 localhost kernel: remove_proc_entry: systemtap/stap_d116efa3785a073ecd3b45ae46950a46_72240 busy, count=1 Sep 17 11:51:20 localhost kernel: remove_proc_entry: /proc/systemtap busy, count=1 ...meaning the deletions have been deferred. 4. Run the procfs probe script again, then CD to /proc. There's no /proc/systemtap entry. I don't see any error messages that indicate /proc/systemtap could not be added. I had to reboot the system before I could get the script to add /proc/systemtap again. -- Summary: procfs probe script not recreating /proc entries in some cases Product: systemtap Version: unspecified Status: NEW Severity: normal Priority: P2 Component: runtime AssignedTo: systemtap at sources dot redhat dot com ReportedBy: mmlnx at us dot ibm dot com http://sourceware.org/bugzilla/show_bug.cgi?id=5042 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.