From: Roland McGrath <roland@redhat.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Ingo Molnar <mingo@redhat.com>, <linux-kernel@vger.kernel.org>
Subject: Re: another subtle signals issue
Date: Tue, 11 Feb 2003 19:50:41 -0800 [thread overview]
Message-ID: <200302120350.h1C3ofQ19892@magilla.sf.frob.com> (raw)
In-Reply-To: Linus Torvalds's message of Tuesday, 11 February 2003 19:18:33 -0800 <Pine.LNX.4.44.0302111912580.2667-100000@home.transmeta.com>
> You just have to read it in a way that says "partial results are
> permissible, and are part of the normal behaviour". And then the fact that
> when ^Z happens you get partial results from pipes is not "different
> behaviour" from a qualitative standpoint - even though in fact we'd get a
> full result if the ^Z didn't happen.
I'm not talking about reading from pipes, that was your example. I was
talking about calls with timeouts, like semop, whose interface do not
permit partial results. Anyway, I find your reading insupportable even in
reference to read or write. read and write are explicitly specified to
return partial results when interrupted by a signal, and are not permitted
to do so otherwise. 1003.1-2001 2.4.4 defines "interrupted" in reference
only to signals that are caught.
next prev parent reply other threads:[~2003-02-12 3:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0302111356550.1405-100000@penguin.transmeta.com>
2003-02-12 2:06 ` Roland McGrath
2003-02-12 2:45 ` Linus Torvalds
2003-02-12 3:05 ` Daniel Jacobowitz
2003-02-12 3:10 ` Linus Torvalds
2003-02-12 3:23 ` Roland McGrath
2003-02-12 3:38 ` Linus Torvalds
2003-02-12 3:13 ` Roland McGrath
2003-02-12 3:18 ` Linus Torvalds
2003-02-12 3:50 ` Roland McGrath [this message]
2003-02-12 4:21 ` Linus Torvalds
2003-02-12 20:12 ` Linus Torvalds
2003-02-12 21:11 ` Roland McGrath
2003-02-12 21:19 ` Linus Torvalds
2003-02-12 21:58 ` Roland McGrath
2003-02-12 21:42 ` Linus Torvalds
2003-02-12 22:04 ` Roland McGrath
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=200302120350.h1C3ofQ19892@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®