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

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

[dwilder at us dot ibm dot com]

Here is the expected results and the real results.  The format of the "times" do
not match(??)  This was observered on a s390.

---cut----
futimes: utime ("foobar", [2001/09/09-01:46:40, 2033/05/18-03:33:20]) = 0
--------- EXPECTED and NOT MATCHED ----------
futimes: utimes \("foobar", \[1000000000.001234\]\[2000000000.005678\]\)

-- 
           Summary: systemtap.syscall/futime test failing.
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: dwilder at us dot ibm dot com


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.

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

[wcohen at redhat dot com]

------- Additional Comments From wcohen at redhat dot com  2007-08-10 14:41 -------
The futimes test has passed on other machines. Does the s390 have a wrapper that
uses utime for utimes? That would explain the differences in the system calls
(utime vs. utimes) and the difference in the argument handling.


-- 


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.

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

[hunt at redhat dot com]

------- Additional Comments From hunt at redhat dot com  2007-08-16 16:03 -------
I'm not sure what is going on here. Please try the following
Do a cvs update
cd to testsuite/systemtap.syscall
compile futimes; gcc -o futimes futimes.c
./all_syscalls.stp -c ./futimes | grep utim
Then post the output here.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hunt at redhat dot com
             Status|NEW                         |WAITING


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.

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

[dwilder at us dot ibm dot com]

------- 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.

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

[dwilder at us dot ibm dot com]

------- Additional Comments From dwilder at us dot ibm dot com  2007-09-11 01:26 -------
It s390 spicific so I will assign it my myself.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED


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.

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

[dwilder at us dot ibm dot com]

------- Additional Comments From dwilder at us dot ibm dot com  2007-09-11 01:28 -------
Woops updated the wrong bug.  Back to systemtap.

-- 


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.

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

[dwilder at us dot ibm dot com]

------- Additional Comments From dwilder at us dot ibm dot com  2007-09-11 03:59 -------
How about 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|systemtap at sources dot    |dwilder at us dot ibm dot
                   |redhat dot com              |com


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.