From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Kent Subject: Re: [PATCH] autofs4 needs to force fail return revalidate Date: Wed, 21 Jun 2006 21:39:25 +0800 (WST) Message-ID: References: <200606210618.k5L6IFDr008176@raven.themaw.net> <20060620233941.49ba2223.akpm@osdl.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: autofs mailing list , linux-fsdevel , Kernel Mailing List Return-path: Received: from wombat.indigo.net.au ([202.0.185.19]:1542 "EHLO wombat.indigo.net.au") by vger.kernel.org with ESMTP id S932151AbWFUNkp (ORCPT ); Wed, 21 Jun 2006 09:40:45 -0400 To: Al Viro , Andrew Morton In-Reply-To: <20060620233941.49ba2223.akpm@osdl.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, 20 Jun 2006, Andrew Morton wrote: > > Also, did you consider broadening the ->d_revalidate() semantics? It > appears that all implementations return 0 or 1. You could teach the VFS to > also recognise and act upon a -ve return value, and do this trickery within > the autofs d_revalidate(), perhaps? > Now it occurs to me this is the only safe way to do this. And a lot simpler. Al, given this is such a heavily traveled piece of code, do you think it would be acceptable to change the semantics of revalidate in this way. Ian