Re: Fwd: NFS locking/acess bug in 2.4.19-rc3

[Neil Brown]

> 
> Subject: NFS locking/acess bug in 2.4.19-rc3
> Date: Tue, 23 Jul 2002 14:31:45 +0400
> To: [e-mail]
> Cc: [e-mail]
> 
> Description of situation.
> 
> NFS server with public file system, export whith options (rw,
> map_daemon, all_squash, anonuid=99, anonguid=99).

I cannot reproduce your problem,  behaviour and code seem correct to
me.

I am suspicious of the "map_daemon" option.
This is not valid for the Kernel NFS server and would not be accepted
by the nfs-utils package.
Are you perhaps using the user-space nfs server (some times called
"nfs-server")?

If so, you should know that:
  The behaviour of the user-space nfs server would not be affect
    (greatly) by the kernel version that you are running
  That server is completely unsupported (as far as I know).

If you are using the  kernel based server, please show me:
  cat /etc/exports
  cat /proc/fs/nfs/exports

and I will try harder to reproduce the problem.

NeilBrown

> 
> Both server and client boxes runs under 2.4.19-rc3.
> 
> Problem:
> 
> When client create catalog in NFS, it normally creates with
> uid=99 guid=99 (i.e. "nobody") and access rwXr-Xr-X.
> 
> This catalog normally deleted by client too.
> 
> But attempting of write file into created catalog from the same
> client failed: "acess denied". File writing is possible only if
> "write" privilegies to this catalog is given to "others", i.e.
> after "chmod "o+w" <catalogname>".
> 
> Analogical situation with files: text editor normally creates
> new file ("save as"), but acess denied to re-writing the
> existant file.
> 
> It's wrong behavior.
> 
> On previous kernel version (pre10) NFS server/clients with the
> same tuning works normally, no access problems detected.
> 
> Bug is application-indepedent and detected both under under KDE
> and MidNight Commander.
> 
> --
> Best regards,
> George
> 
> -------------------------------------------------------