From: Brian Pawlowski <beepy@netapp.com>
To: neilb@cse.unsw.edu.au (Neil Brown)
Cc: akpm@osdl.org, tigran@aivazian.fsnet.co.uk, linux-kernel@vger.kernel.org
Subject: Re: ext3 and SPEC SFS Run rules.
Date: Mon, 26 Jul 2004 16:45:55 -0700 (PDT) [thread overview]
Message-ID: <200407262345.i6QNjtr11774@tooting.eng.netapp.com> (raw)
In-Reply-To: <16645.36138.385234.785650@cse.unsw.edu.au> from Neil Brown at "Jul 27, 4 09:00:58 am"
> The only place that I am aware of where we *do*not* return wcc data is
> for the WRITE request (which you have not listed). As the underlying
> filesystem is left to do whatever locking it thinks is appropriate,
> and vfs_write does none, nfsd is not in a position to lock it itself
> against sys_write and so cannot record before and after stat
> information that is atomic w.r.t the update.
Without replaying conversations on V3 and wcc_ stuff I do believe that
long about 1993 or 1994 most decided that making the pre- and post-stat
info atomic w.r.t. the update was not "required" - because that would
be hard.
The WCC stuff is relegated to a hint to help detect conflicting
changes in that case I believe.
beepy
prev parent reply other threads:[~2004-07-26 23:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 18:49 Tigran Aivazian
2004-07-26 7:03 ` Andrew Morton
2004-07-26 9:12 ` Tigran Aivazian
2004-07-26 9:18 ` Tigran Aivazian
2004-07-28 21:00 ` Andreas Dilger
2004-07-26 19:57 ` Theodore Ts'o
2004-07-26 20:01 ` Andrew Morton
2004-07-26 23:00 ` Neil Brown
2004-07-26 23:45 ` Brian Pawlowski [this message]
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=200407262345.i6QNjtr11774@tooting.eng.netapp.com \
--to=beepy@netapp.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=tigran@aivazian.fsnet.co.uk \
/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®