From owner-freebsd-fs Mon May 12 03:35:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA10674 for fs-outgoing; Mon, 12 May 1997 03:35:45 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA10665 for ; Mon, 12 May 1997 03:35:42 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id LAA06661; Mon, 12 May 1997 11:35:05 +0100 (BST) Date: Mon, 12 May 1997 11:35:05 +0100 (BST) From: Doug Rabson To: pius@ienet.com cc: freebsd-fs@FreeBSD.ORG, terryl@ienet.com Subject: Re: nfs cache permissions problem? In-Reply-To: <199704302151.OAA04610@iago.ienet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 30 Apr 1997 pius@ienet.com wrote: > > On Wed, 30 Apr 1997, dfr@nlsystems.com wrote: > > I know about this problem and there is an open PR for it. I don't know > > what the right fix for it is though. I can't do an ACCESS rpc for every > > cache read (apart from the performance, NFSv2 doesn't have an ACCESS rpc). > > The best I have come up with so far is to somehow associate a cred with > > each buf in the cache and only allow accesses which are allowed by the > > cred. Failures will invalidate the buf and attempt the READ rpc, allowing > > the server to do the check. > > Oops, sorry, I should have checked the PRs first. > > So the fix provided by the originator of kern/2635 would significantly > affect performance? Or perhaps it has other problems? > > Does the NFSv3 implementation fix this? How do other NFS implementations > handle this case (e.g. OpenBSD, NetBSD, Linux, Solaris)? > > Anyways, thanks very much for your help, > Pius > I have committed a fixed for this permission problem to current. Expect a fix to show up in 2.2 within a couple of weeks. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891