This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/6762] New: Some syscalls functions just wrappers for other syscalls
- From: "wcohen at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 23 Jul 2008 21:19:27 -0000
- Subject: [Bug tapsets/6762] New: Some syscalls functions just wrappers for other syscalls
- Reply-to: sourceware-bugzilla at sourceware dot org
When looking through the results of the nightly tests on Red Hat Enterprise
Linux 5 (2.6.18-92.1.6.el5 kernel) a number of the syscall.stp test failed:
FAIL: 64-bit access
FAIL: 64-bit chmod
FAIL: 64-bit forkwait
FAIL: 64-bit link
FAIL: 32-bit access
FAIL: 32-bit chmod
FAIL: 32-bit forkwait
FAIL: 32-bit link
Looking through the output found output like the following for the access test:
access: access ("foobar1", F_OK) =
access: faccessat (AT_FDCWD, "foobar1", F_OK) = 0
0
The sys_access function is just a wrapper for the sys_faccessat function. Thus,
the faccessat output occurs in the middle. This is not what users are expecting.
Look at 2.6.26 kernel also saw similar problems with sys_chmod and sys_creat.
--
Summary: Some syscalls functions just wrappers for other syscalls
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: wcohen at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=6762
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.