This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/6762] Some syscalls functions just wrappers for other syscalls
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 20 Oct 2008 16:50:58 -0000
- Subject: [Bug tapsets/6762] Some syscalls functions just wrappers for other syscalls
- References: <20080723211927.6762.wcohen@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From fche at redhat dot com 2008-10-20 16:50 -------
One possible fix is to extend the syscalls tapset thusly:
# add someplace
global syscall_inplay
probe process.syscall { syscall_inplay[tid()] = $syscall }
probe process.syscall.return { delete syscall_inplay[tid()] }
probe process.thread.end { delete syscall_inplay[tid()] }
# then for each "nestable" system call handler
probe syscall.faccessat = kernel.function(" ...") {
if (syscall_inplay[tid()]) next;
}
Alternately, one can instrument just the "nester" and "nestee" probe
pairs with similar logic, without general system-wide utrace syscall
probes.
Alternately, one can kludge the test case to accept and ignore such
nesting. :-(
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6762
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.