public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: "Zhang, Yanmin" <yanmin.zhang@intel.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 32bit processes at compatbility mode on x86_64 machines fail to restart syscall after processing a signal
Date: Thu, 19 May 2005 03:49:10 +0200	[thread overview]
Message-ID: <m164xgyoh5.fsf@muc.de> (raw)
In-Reply-To: <8126E4F969BA254AB43EA03C59F44E84021E9C58@pdsmsx404> (Yanmin Zhang's message of "Thu, 19 May 2005 09:18:59 +0800")

"Zhang, Yanmin" <yanmin.zhang@intel.com> writes:

> 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).

Thanks for tracking this down. Queued.

-Andi


      reply	other threads:[~2005-05-19  1:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  1:18 32bit processes at compatbility mode on x86_64 machines fail to restart syscall after processing a signal Zhang, Yanmin
2005-05-19  1:49 ` Andi Kleen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m164xgyoh5.fsf@muc.de \
    --to=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yanmin.zhang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox