This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/13452] tapset/nd_syscalls.stp:# FIXME: doesn't handle sys_eventfd2()
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 30 Nov 2011 16:53:02 +0000
- Subject: [Bug tapsets/13452] tapset/nd_syscalls.stp:# FIXME: doesn't handle sys_eventfd2()
- Auto-submitted: auto-generated
- References: <bug-13452-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13452
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dsmith at redhat dot com
Depends on| |11424
--- Comment #1 from David Smith <dsmith at redhat dot com> 2011-11-30 16:53:02 UTC ---
Here's a bit more from tapset/syscalls.stp:
----
# eventfd _____________________________________________________
# long sys_eventfd(unsigned int count)
# SYSCALL_DEFINE2(eventfd2, unsigned int, count, int, flags)
probe syscall.eventfd = kernel.function("sys_eventfd2").call !,
kernel.function("sys_eventfd").call ?
----
The reason why it is done this way is that in the kernel sys_eventfd is just a
wrapper around sys_eventfd2. This way we ignore the sys_eventfd call, and only
catch the sys_eventfd2 call on kernels with sys_eventfd2.
Unfortunately, as bug #11424 notes, '!' (optional and sufficient) doesn't work
for kprobe.function probes. So, the above logic will be difficult to duplicate
in tapset/nd_syscalls.stp.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.