[Bug tapsets/13453] tapset/nd_syscalls.stp:# FIXME: doesn't handle sys_inotify_init1()

["dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=13453

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 17:13:22 UTC ---
The reason why it is done this way in syscalls.stp is that in the kernel
sys_inotify_init is just a wrapper around sys_inotify_init1.  This way we
ignore the sys_inotify_init call, and only catch the sys_inotify_init1 call on
kernels with sys_inotify_init1.

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.