Bug 241408 - utrace breaks PTRACE_SYSEMU: orig_eax value not preserved
Summary: utrace breaks PTRACE_SYSEMU: orig_eax value not preserved
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 6
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Roland McGrath
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-05-25 20:18 UTC by Roland McGrath
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version: 2.6.21-1.2962.fc6
Clone Of:
Environment:
Last Closed: 2007-06-22 21:41:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
test case (1.55 KB, text/plain)
2007-05-25 20:18 UTC, Roland McGrath
no flags Details
refined test case (1.63 KB, text/x-csrc)
2007-05-26 01:27 UTC, Roland McGrath
no flags Details

Description Roland McGrath 2007-05-25 20:18:06 UTC
PTRACE_SYSEMU behavior changed, regression affects UML.

Correct output:

-bash-3.1$ ./ptrace-sysemu 
Status 0x857f eip 8048518 eax -38 orig_eax 20
Status 0xb7f eip 8048518 eax -38 orig_eax -1
PTRACE_GETREGS: No such process
-bash-3.1$ 

Wrong output:

-bash-3.1$ ./ptrace-sysemu 
Status 0x857f eip 8048518 eax -38 orig_eax -1
Status 0xb7f eip 8048518 eax -38 orig_eax -1
PTRACE_GETREGS: No such process
-bash-3.1$

Comment 1 Roland McGrath 2007-05-25 20:18:07 UTC
Created attachment 155480 [details]
test case

Comment 2 Roland McGrath 2007-05-25 22:28:47 UTC
I have a fix in upstream utrace now.

Comment 3 Roland McGrath 2007-05-26 01:27:52 UTC
Created attachment 155493 [details]
refined test case

Expected output now looks like this:

Status 0x857f eip 8048518 eax -38 orig_eax 20
Status 0xb7f eip 8048519 eax -38 orig_eax -1
PTRACE_GETREGS: No such process

Comment 4 Chuck Ebbert 2007-06-22 21:27:54 UTC
Roland, can we close this? (the Jun 14th utrace went into FC6 kernel 2962)

Comment 5 Roland McGrath 2007-06-22 21:41:44 UTC
Yup, it's all good now.  Please close with the right number in currentrelease if
it is pushed.


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