From: David Woodhouse <dwmw2@infradead.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "Bryan Henderson" <hbryan@us.ibm.com>,
David Chow <davidchow@shaolinmicro.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: NFS retry on disconnection
Date: Tue, 14 May 2002 10:30:05 +0100 [thread overview]
Message-ID: <4476.1021368605@redhat.com> (raw)
In-Reply-To: <200205141124.20012.trond.myklebust@fys.uio.no>
trond.myklebust@fys.uio.no said:
> Some things are unavoidable. The standard NFS close-to-open cache
> consistency rules are not, for instance, compatible with 'intr' since
> the latter breaks requirements such as 'close() must wait for all
> data to have been flushed to disk'.
If the sys_close() system call is interrupted, surely it returns -EINTR and
the file is still open? If userspace doesn't check that, this is not our
problem.
And if we _must_ let the sys_close() call succeed even though it was
interrupted, surely we can enforce cache consistency before allowing the
next open() to succeed?
--
dwmw2
next prev parent reply other threads:[~2002-05-14 9:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 16:17 NFS retry on disconnection Bryan Henderson
2002-05-14 6:41 ` David Chow
2002-05-14 7:11 ` Trond Myklebust
2002-05-14 8:55 ` David Woodhouse
2002-05-14 9:24 ` Trond Myklebust
2002-05-14 9:30 ` David Woodhouse [this message]
2002-05-14 9:41 ` Trond Myklebust
2002-05-14 9:46 ` David Woodhouse
2002-05-14 10:11 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2002-05-11 17:41 David Chow
2002-05-12 19:58 ` Trond Myklebust
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=4476.1021368605@redhat.com \
--to=dwmw2@infradead.org \
--cc=davidchow@shaolinmicro.com \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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