linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Theodore Tso <tytso@mit.edu>
Cc: Matthew Wilcox <matthew@wil.cx>,
	Bryan Henderson <hbryan@us.ibm.com>,
	Andreas Dilger <adilger@clusterfs.com>,
	"David H. Lynch Jr." <dhlii@comcast.net>,
	linux-fsdevel@vger.kernel.org
Subject: Re: Read/write counts
Date: Mon, 4 Jun 2007 20:57:16 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706042053340.28373@scrub.home> (raw)
In-Reply-To: <20070604183342.GC19224@thunk.org>

Hi,

On Mon, 4 Jun 2007, Theodore Tso wrote:

> Hmm, I'm not sure I would go that far.  Per the POSIX specification,
> we support the optional BSD-style restartable system calls for signals
> which will avoid short reads; but this is only true if SA_RESTART is
> passed to sigaction().  Without SA_RESTART, we will indeed return
> short reads, as required by POSIX.
> 
> I don't think Linus has said that short reads are always evil; I
> certainly can't remember him ever making that statement.  Do you have
> a pointer to a LKML message where he's said that?

That's the last discussion about signals and I/O I can remember:
http://www.ussg.iu.edu/hypermail/linux/kernel/0208.0/0188.html

bye, Roman

  reply	other threads:[~2007-06-04 18:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04 10:20 Read/write counts David H. Lynch Jr.
2007-06-04 16:33 ` Andreas Dilger
2007-06-04 16:56   ` Bryan Henderson
2007-06-04 17:02     ` Matthew Wilcox
2007-06-04 18:33       ` Theodore Tso
2007-06-04 18:57         ` Roman Zippel [this message]
2007-06-04 19:24           ` Joel Becker
2007-06-04 20:00           ` Theodore Tso

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=Pine.LNX.4.64.0706042053340.28373@scrub.home \
    --to=zippel@linux-m68k.org \
    --cc=adilger@clusterfs.com \
    --cc=dhlii@comcast.net \
    --cc=hbryan@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --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;
as well as URLs for NNTP newsgroup(s).