Re: nfs insecure_locks / Tru64 behaviour

[Trond Myklebust <trond.myklebust@fys.uio.no>]

On Fri, 2005-12-23 at 08:38 -0500, Ron Peterson wrote:
> The gid's of the kmw group match on both sides.  The problem happens
> whether root squashing is on or off.  Unless the execute bit for 'other'
> is turned on for the parent directory, the file appears to be locked
> when being accessed from the nfs client (tru64) side.
> 
> My theory may be wrong, but the problem still exists.

Possibly, but that sounds like it might be a tru64 bug. As you can see,
a Linux client has no such problems:

[trondmy@longyearbyen trondmy]$ id
uid=520(trondmy) gid=100(users) groups=10(wheel),100(users)
[trondmy@longyearbyen trondmy]$ ls -al
total 0
drwxr-xr-x  5 trondmy users 36 Dec 23 08:44 .
drwxr-xr-x  3 root    root  20 Jun 17  2005 ..
drwxr-x---  2 root    users 18 Dec 23 08:47 d
drwxr-xr-x  8 root    root  68 Dec  5 01:11 gnurr
drwxr-xr-x  2 trondmy users 30 Nov 23 10:38 tmp
[trondmy@longyearbyen trondmy]$ ls -al d
total 4
drwxr-x---  2 root    users 18 Dec 23 08:47 .
drwxr-xr-x  5 trondmy users 36 Dec 23 08:44 ..
-rw-r--r--  1 root    root   6 Dec 23 08:47 hello
[trondmy@longyearbyen trondmy]$ cat d/hello
hello

Cheers,
  Trond

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/