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


trond.myklebust@fys.uio.no said:
>  Look at the code for close on exit. I can't see that those EINTRs
> actually do  get propagated to userland. 

True. I suppose you could make a case for ignoring signals in the
close-on-exit case, or just attempt to do the flush as soon as possible 
thereafter. Are there any other cases where it's actually a problem?

--
dwmw2