This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/5042] New: procfs probe script not recreating /proc entries in some cases
- From: "mmlnx at us dot ibm dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 17 Sep 2007 19:15:22 -0000
- Subject: [Bug runtime/5042] New: procfs probe script not recreating /proc entries in some cases
- Reply-to: sourceware-bugzilla at sourceware dot org
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.