[Bug tapsets/6762] Some syscalls functions just wrappers for other syscalls

[dsmith at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=6762

David Smith <dsmith at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #5 from David Smith <dsmith at redhat dot com> ---
(In reply to Frank Ch. Eigler from comment #4)
> This problem periodically reoccurs; we will have to deal with it
> properly.  See bug #11263.

As part of all the syscall tapset work that's been done recently (bug #16716),
a fix to avoid syscall nesting has been developed (originally for bug #15219).
This fix involves use of the @__syscall_gate() family of macros. This fix
basically says if we're in syscall.faccessat, but the syscall number isn't
__NR_faccessat, return.

Every known instance of this problem has been fixed. It is likely there are
problems with syscalls without a test program. We'll have to tackle these as we
continue work in this area.

I'm going mark this bug as resolved, and we'll just file individual bugs on
syscalls without test programs and fix nesting problems then.

-- 
You are receiving this mail because:
You are the assignee for the bug.