diff options
| author | Andi Kleen <ak@suse.de> | 2005-05-20 14:27:58 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-05-20 15:48:21 -0700 |
| commit | 607a16858397829806c5a4db999ce6daf327f98c (patch) | |
| tree | 10f3568581880d54287382dcdfb02dcc5525df8e /Documentation/x86_64 | |
| parent | 4057923614e2868a865aa6c6e3bc53542c818d4d (diff) | |
| download | linux-3.10-607a16858397829806c5a4db999ce6daf327f98c.tar.gz linux-3.10-607a16858397829806c5a4db999ce6daf327f98c.tar.bz2 linux-3.10-607a16858397829806c5a4db999ce6daf327f98c.zip | |
[PATCH] x86_64: Fix 32bit system call restart
The test case at
http://cvs.sourceforge.net/viewcvs.py/posixtest/posixtestsuite/conforman
ce/interfaces/clock_nanosleep/1-5.c fails if it runs as a 32bit process on
x86_86 machines.
The root cause is the sub 32bit process fails to restart the syscall after it
is interrupted by a signal.
The syscall number of sys_restart_syscall in table sys_call_table is
__NR_restart_syscall (219) while it's __NR_ia32_restart_syscall
(0) in ia32_sys_call_table. When regs->rax==(unsigned
long)-ERESTART_RESTARTBLOCK, function do_signal doesn't distinguish if
the process is 64bit or 32bit, and always sets restart syscall number
as __NR_restart_syscall (219).
Signed-off-by: Zhang Yanmin <yanmin.zhang@intel.com>
Signed-off-by: Andi Kleen <ak@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'Documentation/x86_64')
0 files changed, 0 insertions, 0 deletions