Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 14 Aug 2002 21:33:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 14 Aug 2002 21:33:43 -0400 Received: from pc2-cwma1-5-cust12.swa.cable.ntl.com ([80.5.121.12]:55802 "EHLO irongate.swansea.linux.org.uk") by vger.kernel.org with ESMTP id ; Wed, 14 Aug 2002 21:33:42 -0400 Subject: Re: Will NFSv4 be accepted? From: Alan Cox To: Dax Kelson Cc: "Kendrick M. Smith" , "linux-kernel@vger.kernel.org" , "nfs@lists.sourceforge.net" In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 15 Aug 2002 02:35:27 +0100 Message-Id: <1029375327.28240.35.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1134 Lines: 26 On Thu, 2002-08-15 at 02:27, Dax Kelson wrote: > On 15 Aug 2002, Alan Cox wrote: > > > Thats not an NFS2 or NFS3 issue, thats an implementation matter. A > > proper NFS credential system prevents that from occurring. You also have > > to fix some bogon assumptions in our NFS client too I grant. > > Please, do tell. Ok item #1 you authenticate with the server and get a cryptographic key for use as credentials. This solves the bad client problem. Kerberos, gssapi etc will do the job Item #2 is a bug in our NFS page cache handling. Its not legal in NFS to assume we can share caches between processes unless they have the same NFS credentials for the query. The most we can do (and should do) is that when we think we can reuse a cache entry we issue an NFS ACCESS check for NFSv3 or for NFSv2 we write it back to the server if dirty then issue a read for the new credential set. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/