From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Woodhouse Subject: Re: NFS retry on disconnection Date: Tue, 14 May 2002 10:30:05 +0100 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <4476.1021368605@redhat.com> References: <200205141124.20012.trond.myklebust@fys.uio.no> <200205140911.50503.trond.myklebust@fys.uio.no> <972.1021366509@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Bryan Henderson" , David Chow , linux-fsdevel@vger.kernel.org Return-path: In-Reply-To: <200205141124.20012.trond.myklebust@fys.uio.no> To: Trond Myklebust List-Id: linux-fsdevel.vger.kernel.org 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