This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/16861] New: probes aren't re-registered after module reload
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Mon, 21 Apr 2014 20:36:17 +0000
- Subject: [Bug runtime/16861] New: probes aren't re-registered after module reload
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=16861
Bug ID: 16861
Summary: probes aren't re-registered after module reload
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: jistone at redhat dot com
With emit_module_refresh, we can support probes in modules that weren't loaded
at the time stap started. However, if a module is unloaded and then loaded
again, we miss the chance to register the probes anew.
For example, on a system not already using btrfs.ko:
$ stap -e 'probe module("btrfs").function("*_btrfs_fs").call {
println(ppfunc()) }' -c 'sudo sh -c "modprobe btrfs; modprobe -r btrfs;
modprobe btrfs; modprobe -r btrfs"'
init_btrfs_fs
exit_btrfs_fs
The init and exit are only noticed once, despite being loaded twice.
--
You are receiving this mail because:
You are the assignee for the bug.