Bug 159790 - ptrace changes to registers during ia32 syscall tracing stop are lost
ptrace changes to registers during ia32 syscall tracing stop are lost
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Roland McGrath
Brian Brock
Depends On:
Blocks: 156320 158925
  Show dependency treegraph
Reported: 2005-06-07 19:54 EDT by Roland McGrath
Modified: 2007-11-30 17:07 EST (History)
3 users (show)

See Also:
Fixed In Version: RHSA-2005-663
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-28 11:16:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
RHEL3 kernel patch fixing this bug (576 bytes, patch)
2005-06-07 19:54 EDT, Roland McGrath
no flags Details | Diff

  None (edit)
Description Roland McGrath 2005-06-07 19:54:23 EDT
When an ia32 process is stopped for syscall tracing, ptrace can be used to
modify its registers and that should change the register arguments seen by the
system call.  strace relies on this facility.

In the RHEL3 kernel, changes to registers that aren't used for 64-bit arguments
are lost.
Comment 1 Roland McGrath 2005-06-07 19:54:23 EDT
Created attachment 115202 [details]
RHEL3 kernel patch fixing this bug
Comment 2 Ernie Petrides 2005-06-08 20:12:53 EDT
Patch posted for internal review on 7-Jun-2005.
Comment 4 Ernie Petrides 2005-06-14 21:01:32 EDT
A fix for this problem has just been committed to the RHEL3 U6
patch pool this evening (in kernel version 2.4.21-32.8.EL).
Comment 11 Red Hat Bugzilla 2005-09-28 11:16:54 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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