From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jim Nance <jlnance@us54.synopsys.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
jlnance@unity.ncsu.edu, linux-kernel@vger.kernel.org,
gary.nifong@synopsys.COM, James.Nance@synopsys.COM,
david.thomas@synopsys.COM
Subject: Re: NFS problems with Linux-2.4
Date: 18 May 2003 17:00:24 +0200 [thread overview]
Message-ID: <shsznlkjo53.fsf@charged.uio.no> (raw)
In-Reply-To: <20030515112231.A28148@synopsys.com>
Sorry. stat doesn't obey close-to-open. It relies on standard
attribute caching. close-to-open means "open()" (and only "open()")
checks data cache consistency...
Cheers,
Trond
next prev parent reply other threads:[~2003-05-18 14:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 14:50 NFS problems with Linux-2.4 jlnance
2003-05-13 15:19 ` Trond Myklebust
2003-05-15 15:22 ` Jim Nance
2003-05-18 15:00 ` Trond Myklebust [this message]
2003-05-19 0:53 ` jlnance
2003-05-19 11:27 ` Trond Myklebust
2003-05-19 20:02 ` Jim Nance
2003-05-13 19:07 ` jjs
2003-05-13 19:24 ` Roland Dreier
2003-05-13 21:55 ` jjs
2003-05-13 23:11 ` Alan Cox
[not found] <482A3FA0050D21419C269D13989C6113127532@lavender-fe.eng.netapp.com>
2003-05-27 17:29 ` jlnance
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=shsznlkjo53.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=James.Nance@synopsys.COM \
--cc=david.thomas@synopsys.COM \
--cc=gary.nifong@synopsys.COM \
--cc=jlnance@unity.ncsu.edu \
--cc=jlnance@us54.synopsys.com \
--cc=linux-kernel@vger.kernel.org \
/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