Bug 160049
Summary: | x86-64 on 32-bit vdso syscall entry, %ebp value is not seen in %rbp via ptrace | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Bastien Nocera <bnocera> |
Component: | kernel | Assignee: | Roland McGrath <roland> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | jparadis, mwesley, peterm, petrides, tao |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-19 19:00:42 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 162467 | ||
Bug Blocks: | 170417 |
Description
Bastien Nocera
2005-06-10 14:35:20 UTC
The actual bug here is that the x86-64 kernel doing syscall tracing of a 32-bit process fails to reflect the %ebp value in %rbp, and so is inconsistent with what native 32-bit ptrace shows. This bug exists in the upstream kernel as well. There are two bugs in the original report. This bug is tracking the kernel bug that gives wrong results for the mmap2 syscall, which is what the test case source mentions. However, the original complaints were about the old_mmap syscall output, which is an strace bug #162467 tracks now. This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |