From: Russ Allbery <rra@stanford.edu>
To: Zack Weinberg <zack@codesourcery.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: close return value (was Re: [ANNOUNCE] Ext3 vs Reiserfs benchmarks)
Date: Tue, 16 Jul 2002 20:46:20 -0700 [thread overview]
Message-ID: <ylador3tkj.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <fa.i1e82rv.1digoa4@ifi.uio.no> (Zack Weinberg's message of "Tue, 16 Jul 2002 23:23:34 GMT")
Zack Weinberg <zack@codesourcery.com> writes:
> Consider: There is no guarantee that close will detect errors. Only
> NFS and Coda implement f_op->flush methods.
And AFS, I believe. (Not in the standard kernel, of course.)
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next parent reply other threads:[~2002-07-17 3:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.lfdnrtv.5h8i1j@ifi.uio.no>
[not found] ` <fa.i1e82rv.1digoa4@ifi.uio.no>
2002-07-17 3:46 ` Russ Allbery [this message]
2002-07-16 19:38 [ANNOUNCE] Ext3 vs Reiserfs benchmarks Thunder from the hill
2002-07-16 23:22 ` close return value (was Re: [ANNOUNCE] Ext3 vs Reiserfs benchmarks) Zack Weinberg
2002-07-17 1:03 ` Alan Cox
2002-07-17 0:10 ` Zack Weinberg
2002-07-17 1:45 ` Alan Cox
2002-07-17 18:24 ` Zack Weinberg
2002-07-22 16:42 ` Rogier Wolff
2002-07-17 8:00 ` Lars Marowsky-Bree
2002-07-17 15:49 ` Thunder from the hill
2002-07-17 2:22 ` Elladan
2002-07-17 2:54 ` Thunder from the hill
2002-07-17 3:00 ` Elladan
2002-07-17 3:10 ` Thunder from the hill
2002-07-17 3:31 ` Elladan
2002-07-17 4:17 ` Stevie O
2002-07-17 4:38 ` Elladan
2002-07-17 14:39 ` Andreas Schwab
2002-07-17 16:49 ` Elladan
2002-07-17 17:43 ` Linus Torvalds
2002-07-17 22:07 ` Elladan
2002-07-18 9:48 ` Ketil Froyn
2002-07-17 17:17 ` Andries Brouwer
2002-07-17 17:51 ` Richard Gooch
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=ylador3tkj.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=zack@codesourcery.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 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.