From owner-freebsd-bugs Mon Oct 20 20:20:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA13165 for bugs-outgoing; Mon, 20 Oct 1997 20:20:03 -0700 (PDT) (envelope-from owner-freebsd-bugs) Received: (from gnats@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA13132; Mon, 20 Oct 1997 20:20:01 -0700 (PDT) (envelope-from gnats) Date: Mon, 20 Oct 1997 20:20:01 -0700 (PDT) Message-Id: <199710210320.UAA13132@hub.freebsd.org> To: freebsd-bugs Cc: From: Bruce Evans Subject: Re: bin/4805: NFSv3 server readonly file permission problem Reply-To: Bruce Evans Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/4805; it has been noted by GNATS. From: Bruce Evans To: FreeBSD-gnats-submit@FreeBSD.ORG, sanpei@yy.cs.keio.ac.jp Cc: Subject: Re: bin/4805: NFSv3 server readonly file permission problem Date: Tue, 21 Oct 1997 13:09:48 +1000 >>How-To-Repeat: > >1. create readonly file on NFS server >-r--r--r-- 1 sanpei yamamoto 1421 Oct 19 23:54 test >... >case C [problem] >NFS server FreeBSD 2.2.2-R >NFS client FreeBSD 2.2.5-BETA and nfs**v3** mount > >open read/write mode and it can be editted and written by save-file. This is also broken with a FreeBSD-current client and server. The problem seems to be that nfsrv_access() pretends that the permissions are 777 for the owner of the file. nfsV2 clients apparently understand this, but nfsrv_access() is used internally by V3 parts of the server, and the server doesn't understand itself. This seems to be fixed in NetBSD by passing an `override' arg to nfsrv_access() to tell it when to fudge the permissions. Bruce