From: Jakub Jelinek <jakub@redhat.com>
To: Michael Kerrisk <michael.kerrisk@gmx.net>
Cc: Arjan van de Ven <arjan@infradead.org>,
mtk-manpages@gmx.net, mtk-lkml@gmx.net, rlove@rlove.org,
roland@redhat.com, eggert@cs.ucla.edu, torvalds@osdl.org,
tytso@mit.edu, linux-kernel@vger.kernel.org,
manfred@colorfullife.com, drepper@redhat.com
Subject: Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
Date: Fri, 7 Jul 2006 05:26:36 -0400 [thread overview]
Message-ID: <20060707092636.GU3115@devserv.devel.redhat.com> (raw)
In-Reply-To: <20060707080212.186780@gmx.net>
On Fri, Jul 07, 2006 at 10:02:12AM +0200, Michael Kerrisk wrote:
> There have been ABI changes in the past. In the end, I assume
> it's a question of relative desirability ("how broken is existing
> behaviour"; or: "was that behaviour ever desirable/portable
> anyway?") versus relative likelihood of breaking applications.
In futex(2) case (except FUTEX_LOCK_PI where we want it to be restartable),
getting EINTR rather than the getting the syscall restarted is very
desirable though and several NPTL routines rely on it.
Jakub
next prev parent reply other threads:[~2006-07-07 9:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 14:46 Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT Michael Kerrisk
2006-07-04 19:02 ` Manfred Spraul
2006-07-06 9:23 ` Michael Kerrisk
2006-07-06 18:42 ` Manfred Spraul
2006-07-06 18:55 ` Ulrich Drepper
2006-07-06 19:02 ` Manfred Spraul
2006-07-06 19:10 ` Ulrich Drepper
2006-07-06 19:18 ` Linus Torvalds
2006-07-06 19:28 ` Manfred Spraul
2006-07-06 19:29 ` Manfred Spraul
2006-07-07 4:57 ` Michael Kerrisk
2006-07-07 5:10 ` Linus Torvalds
2006-07-07 5:12 ` Linus Torvalds
2009-11-07 19:43 ` angelo.borsotti
2006-07-07 4:32 ` Michael Kerrisk
2006-07-07 4:57 ` Ulrich Drepper
2006-07-07 5:07 ` Michael Kerrisk
2006-07-07 6:20 ` Ulrich Drepper
2006-07-07 7:03 ` Michael Kerrisk
2006-07-07 7:20 ` Arjan van de Ven
2006-07-07 8:02 ` Michael Kerrisk
2006-07-07 9:26 ` Jakub Jelinek [this message]
2006-07-07 13:36 ` Ulrich Drepper
2006-07-07 4:28 ` 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=20060707092636.GU3115@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=arjan@infradead.org \
--cc=drepper@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=michael.kerrisk@gmx.net \
--cc=mtk-lkml@gmx.net \
--cc=mtk-manpages@gmx.net \
--cc=rlove@rlove.org \
--cc=roland@redhat.com \
--cc=torvalds@osdl.org \
--cc=tytso@mit.edu \
/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