NetBSD Problem Report #10845

Received: (qmail 23174 invoked from network); 16 Aug 2000 11:38:42 -0000
Message-Id: <>
Date: Wed, 16 Aug 2000 12:38:02 +0100 (BST)
Subject: Broken NFS permissions checking when -mapall=user is used.
X-Send-Pr-Version: 3.95

>Number:         10845
>Category:       kern
>Synopsis:       Broken NFS permissions checking when -mapall=user is used.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Aug 16 11:39:00 +0000 2000
>Last-Modified:  Thu Mar 22 03:55:07 +0000 2001
>Originator:     Steve Woodford
>Release:        1.5_ALPHA2
	NetBSD NFS Server,
	Solaris NFS Clients
System: NetBSD haggis 1.5_ALPHA2 NetBSD 1.5_ALPHA2 (HAGGIS) #0: Wed Aug 16 08:23:13 BST 2000 swoodfor@haggis:/u0/netbsd/src/sys/arch/i386/compile/HAGGIS i386

When a NetBSD file-system is NFS exported with the -mapall=nobody (for example)
option in the /etc/exports file, you would expect that NFS clients would be
able to change certain attributes of files on that FS which are owned by

Currently, when the NFS client issues a utimes(2) system call on a file
it just created on the NFS file-system, that system call returns EACCESS.
Presumably the server is not taking the -mapall=nobody into account when
evaluating permission for that operation.

It's likely this affects other operations, as a coworker just reported having
the same problem with chmod(1)...
Make an entry in an NFS server's /etc/exports with the -mapall=nobody option.
Mount the filesystem on a client (in this case Solaris, but that may not
matter) and create a new file; it should be owned and writable by `nobody'.
Try to modify the access time of the file using `touch -c'.
No idea.

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD:,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.