This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/13454] nd_syscall tapset needs to handle sys_pipe2 and pipe0/pipe1
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 30 Nov 2011 18:38:48 +0000
- Subject: [Bug tapsets/13454] nd_syscall tapset needs to handle sys_pipe2 and pipe0/pipe1
- Auto-submitted: auto-generated
- References: <bug-13454-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13454
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:38:48 UTC ---
>From syscalls2.stp:
----
# pipe _______________________________________________________
#
# asmlinkage int
# sys_pipe(unsigned long __user * fildes)
#
# SYSCALL_DEFINE2(pipe2, int __user *, fildes, int, flags)
# pipe2() was added to Linux in version 2.6.27.
probe syscall.pipe = kernel.function("sys_pipe2").call !,
kernel.function("sys_ia64_pipe").call ?,
kernel.function("sys_pipe").call
----
The reason why it is done this way is that in the kernel
sys_pipe is just a wrapper around sys_pipe2. This way we
ignore the sys_pipe call, and only catch the sys_pipe2 call on
kernels with sys_pipe2.
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_syscalls2.stp.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.