On Sun, 26 Mar 2006, Han Boetes wrote:

> Hi,
>
> OpenBSD is the NFS-server OS; Linux is the client OS.
>
> ~% ls -l /home/public/han/nowplaying*
> -rw-rw-r-- 1 han nfs 87 Mar 26 20:39 nfs/nowplaying
> -rw-rw-r-- 1 han nfs 89 Mar 26 20:39 nfs/nowplayingice
>
>
> On my Linux machine I have a restricted account which is member of
> the group nfs and therefore should have permissions to write to
> this file, allas it has not.
>
> Actually at first I thought it was a Linux kernel error but after
> reporting the bug and talking with the maintainer he found out it
> was an OpenBSD-NFS bug.
>
> Read here if you are interested in the full discussion.
> http://bugzilla.kernel.org/show_bug.cgi?id=6256
>
> You can also find the result of `sudo tcpdump -s9000 -c100 -w file
> -Nt udp port 2049' here:
> http://bugzilla.kernel.org/attachmen...19&action=view
>
> Which contains a .gz file with the evidence that OpenBSD does
> something wrong.
>
> This also seems to be related to the owned of the directory in
> which the file exists. IE, if I changed the owner of the file to
> the restricted account, my own account -- also member of the nfs
> group -- still could write to the file.

Can or cannot?

> This is the matching line in exports:
> /home/public/han -maproot=han:nfs marsupilami

I am almost able to reproduce:

I can edit the file (using vi or redirection form the shell)
But a setattr call fails, I cannot touch(1) the file, for example.

For some reason your test generates a setattr call, which is normally
not done for writing a file.

I'll investigate more.

$ ls -al
total 16
drwxr-xr-x 2 otto wsrc 512 Mar 26 21:35 .
drwxr-xr-x 77 otto otto 5632 Mar 26 21:35 ..
-rw-rw-r-- 1 otto wsrc 0 Mar 26 22:26 aap
$ id
uid=999(test) gid=999(test) groups=999(test), 9(wsrc)
$ echo foo > aap
$ cat aap
foo
$ touch aap
touch: aap: Operation not permitted
$
-Otto