[Bug testsuite/4902] systemtap.syscall/futime test failing.

["dwilder at us dot ibm dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From dwilder at us dot ibm dot com  2007-09-06 17:22 -------
Here is th output you wanted.  (this is from the the 9/1 snapshot. I did not do
the cvs update.  Is there a change you needed me to pickup?  Do to firewalls I
can run cvs update directly on the target system.  But will update the code if
it is needed)

kernel.function("sys_utime@fs/utimes.c:26")
kernel.function("sys_utime@fs/utimes.c:26")
kernel.function("sys_futimesat@fs/utimes.c:158")
kernel.function("sys_futimesat@fs/utimes.c:158")

Clearly userspace is mapping utimes to utime.  Here is strace output of the same.
futimes.creat("foobar", 0666)                   = 3
utime("foobar", [2001/09/08-18:46:40, 2033/05/17-20:33:20]) = 0
utime("/proc/self/fd/3", [2001/09/08-18:46:40, 2033/05/17-20:33:20]) = 0
futimesat(7, "foobar", {1000000000, 1234}) = -1 EBADF (Bad file descriptor)
futimesat(AT_FDCWD, "foobar", {1000000000, 1234}) = 0
exit_group(0)                           = ?

I am not sure why the mapping is done as both utimes and utime syscalls are
defined in the kernel.  I don't see much we can do here other than make a s390
spicific test or just make it a KFAIL on S390.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW


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

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