From: Parag Warudkar <kernel-stuff@comcast.net>
To: Roland McGrath <roland@redhat.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
"David S. Miller" <davem@davemloft.net>,
akpm@osdl.org, mtk-lkml@gmx.net, linux-kernel@vger.kernel.org,
michael.kerrisk@gmx.net
Subject: Re: waitid() fails with EINVAL for SA_RESTART signals
Date: Thu, 26 May 2005 20:03:28 -0400 [thread overview]
Message-ID: <200505262003.29228.kernel-stuff@comcast.net> (raw)
In-Reply-To: <200505262322.j4QNMnd9011168@magilla.sf.frob.com>
On Thursday 26 May 2005 19:22, Roland McGrath wrote:
> > x86 has largely tried to move in that direction too, ie a lot of the
> > asm-calls have been turned into FASTCALL() with %eax pointing to the
> > stack.
> >
> > Roland, I applied the patch, but if there was some particular case that
> > triggered this, maybe it's worth trying to re-write that one.
>
> It's a danger for any system call. Here it was sys_waitid.
On X86_64 the given program fails with Operation Not Supported error on
waitid() - both 32bit and 64bit modes. The problem seems to be WCONTINUED -
is it unimplemented on X86_64?
next prev parent reply other threads:[~2005-05-27 0:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 8:20 waitid() fails with EINVAL for SA_RESTART signals Michael Kerrisk
2005-05-26 21:17 ` Roland McGrath
2005-05-26 22:21 ` [PATCH] i386: fix prevent_tail_call Roland McGrath
2005-05-26 22:22 ` waitid() fails with EINVAL for SA_RESTART signals Roland McGrath
2005-05-26 22:37 ` David S. Miller
2005-05-26 23:19 ` Linus Torvalds
2005-05-26 23:22 ` Roland McGrath
2005-05-27 0:03 ` Parag Warudkar [this message]
2005-05-27 0:11 ` Roland McGrath
2005-05-27 0:37 ` Parag Warudkar
2005-05-27 1:05 ` Parag Warudkar
2005-05-27 2:01 ` Parag Warudkar
2005-05-30 16:55 ` Michael Kerrisk
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=200505262003.29228.kernel-stuff@comcast.net \
--to=kernel-stuff@comcast.net \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.kerrisk@gmx.net \
--cc=mtk-lkml@gmx.net \
--cc=roland@redhat.com \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.