This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/13455] tapset/nd_syscalls2.stp:# FIXME: should prefer sys_signalfd4
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 30 Nov 2011 18:40:38 +0000
- Subject: [Bug tapsets/13455] tapset/nd_syscalls2.stp:# FIXME: should prefer sys_signalfd4
- Auto-submitted: auto-generated
- References: <bug-13455-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13455
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 18:40:38 UTC ---
The reason why it is done this way in syscalls.stp is that in the kernel
sys_signalfd is just a wrapper around sys_signalfd4. This way we
ignore the sys_signalfd call, and only catch the sys_signalfd4 call on
kernels with sys_signalfd4.
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.