[Bug tapsets/4553] New: i686 RHEL4u5 systemcall tapset argument issues with 2.6.9-55.ELsmp kernel

[Bug tapsets/4553] New: i686 RHEL4u5 systemcall tapset argument issues with 2.6.9-55.ELsmp kernel

[wcohen at redhat dot com]

A number of the systemtap runtime tests fail on the 2.6.9-55.ELsmp kernel
because the the arguments for the systemcalls are not be generated correctly for
the kernel.

FAIL: 32-bit access
FAIL: 32-bit alarm
FAIL: 32-bit chmod
FAIL: 32-bit clock
FAIL: 32-bit dir
FAIL: 32-bit link
FAIL: 32-bit mmap
FAIL: 32-bit mount
FAIL: 32-bit net1
FAIL: 32-bit openclose
FAIL: 32-bit readwrite
FAIL: 32-bit rt_signal
FAIL: 32-bit signal
FAIL: 32-bit stat
FAIL: 32-bit statfs
FAIL: 32-bit swap
FAIL: 32-bit sync
FAIL: 32-bit timer
FAIL: 32-bit trunc
FAIL: 32-bit uid
FAIL: 32-bit uid16
FAIL: 32-bit unlink


Looking through the systemtap.log shows that many of the arguments are listed as
"<unknown>". For example output of 32-bit link includes the following output:

link: open (<unknown>,
O_RDONLY|O_APPEND|O_DIRECTORY|O_EXCL|O_LARGEFILE|O_NONBLOCK) = 4
link: close (4) = 0
link: link (<unknown>, <unknown>) = 0
link: link (<unknown>, <unknown>) = -17 (EEXIST)
link: link (<unknown>, <unknown>) = -2 (ENOENT)
link: symlink (<unknown>, <unknown>) = 0
link: readlink (<unknown>, 0x3a080300, 128) = 6
link: exit_group (0) =

-- 
           Summary: i686 RHEL4u5 systemcall tapset argument issues with
                    2.6.9-55.ELsmp kernel
           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
  GCC host triplet: i686


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

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

[Bug tapsets/4553] i686 RHEL4u5 systemcall tapset argument issues with 2.6.9-55.ELsmp kernel

[wcohen at redhat dot com]

------- Additional Comments From wcohen at redhat dot com  2007-06-07 16:29 -------
Did some searching through the email archive of test results. It looks like
something changed between the following dates to make it so that the tests fails.

worked
Date: 200612200930
User: wcohen
Kernel: Linux 2.6.9-42.0.3.EL #1 Mon Sep 25 17:14:19 EDT 2006 i686 athlon i386
GNU/Linux



failed
Date: 200701120930
User: wcohen
Kernel: Linux 2.6.9-42.0.3.EL #1 Mon Sep 25 17:14:19 EDT 2006 i686 athlon i386
GNU/Linux



-- 


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

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

[Bug tapsets/4553] i686 RHEL4u5 systemcall tapset argument issues with 2.6.9-55.ELsmp kernel

[dsmith at redhat dot com]

------- Additional Comments From dsmith at redhat dot com  2007-06-07 21:01 -------
It looks like RHEL4u5 (or any other system with gcc version < 4) needs the new
"--enable-prologues" configure option.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|systemtap at sources dot    |dsmith at redhat dot com
                   |redhat dot com              |
             Status|NEW                         |ASSIGNED


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

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

[Bug tapsets/4553] i686 RHEL4u5 systemcall tapset argument issues with 2.6.9-55.ELsmp kernel

[dsmith at redhat dot com]

------- Additional Comments From dsmith at redhat dot com  2007-06-08 18:14 -------
I've checked in a change to configure.ac/configure that automatically enables
prologue searching if:
- we're running on an x86
- gcc version is less than 4

This change reduces the cases of system calls returning "<unknown>".  However,
the syscall tests still don't pass.  It appears that on the two rhel4 systems I
tried this on probes get skipped which changes the output the tests look for.

I'm unsure as to why this is happening.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|dsmith at redhat dot com    |systemtap at sources dot
                   |                            |redhat dot com


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

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

[Bug tapsets/4553] i686 RHEL4u5 systemcall tapset argument issues with 2.6.9-55.ELsmp kernel

[dsmith at redhat dot com]

------- Additional Comments From dsmith at redhat dot com  2010-01-14 17:03 -------
On current rhel5 kernels (2.6.18-164.9.1.el5) we don't see this problem, so I'm
closing this as WONTFIX.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dsmith at redhat dot com
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |WONTFIX


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

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