Bug 438614 - utrace: syscall-reset: syscall number change: biarch run FAILs
utrace: syscall-reset: syscall number change: biarch run FAILs
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Roland McGrath
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-03-22 17:50 EDT by Jan Kratochvil
Modified: 2008-03-23 08:52 EDT (History)
1 user (show)

See Also:
Fixed In Version: kernel-2.6.25-0.139.rc6.git5.fc9.x86_64
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-03-23 08:52:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Kratochvil 2008-03-22 17:50:41 EDT
Description of problem:
Tracking a `syscall-reset' testcase bug for i386-debugger-on-x86_64-kernel.

Version-Release number of selected component (if applicable):
kernel- (biarch: -m32)
Working for native variants:
kernel- (-m32)
kernel- (-m64)

How reproducible:

Steps to Reproduce:
1. wget -O syscall-reset.c
2. gcc -o syscall-reset syscall-reset.c -Wall -ggdb2 -D_GNU_SOURCE -m32
3. ./syscall-reset; echo $?

Actual results:

Expected results:

Additional info:
non-biarch (native arch size) runs work fine.

Rawhide kernel-2.6.25-0.121.rc5.git4.fc9.x86_64 - non-utrace one, based on
2.6.25-rc5-git4 - fails both natively (-m64) and biarch (-m32).
Comment 1 Roland McGrath 2008-03-22 18:05:10 EDT
No upstream kernel did this right for 32-bit ptrace callers on x86_64 in the past.
We probably won't worry about it for any pre-2.6.25 kernel in Fedora.
So this bug should be for rawhide/f9 if those kernels have a problem.
F8 update kernels will probably be 2.6.25 eventually after F9 kernels are stable.
Comment 2 Jan Kratochvil 2008-03-22 18:25:43 EDT
Waiting till a new rawhide utrace lands - rawhide ptrace is broken (Comment 0

Note You need to log in before you can comment on or make changes to this bug.