Joerg Wunsch ec05e1f5d7 The duplicate information returned in fa_type and fa_mode ... is an ambiguity in the NFS version 2 protocol. VREG should be taken literally as a regular file. If a server intents to return some type information differently in the upper bits of the mode field (e.g. for sockets, or FIFOs), NFSv2 mandates fa_type to be VNON. Anyway, we leave the examination of the mode bits even in the VREG case to avoid breakage for bogus servers, but we make sure that there are actually type bits set in the upper part of fa_mode (and failing that, trust the va_type field). NFSv3 cleared the issue, and requires fa_mode to not contain any type information (while also introduing sockets and FIFOs for fa_type). The fix has been tested against a variety of NFS servers. It fixes problems with the ``Tropic'' NFS server for Windows, while apparently not breaking anything. Pointed-out by: scott@zorch.sf-bay.org (Scott Hazen Mueller)		1995-06-14 06:23:38 +00:00
..
nfs_bio.c
nfs_common.c	The duplicate information returned in fa_type and fa_mode	1995-06-14 06:23:38 +00:00
nfs_common.h
nfs_node.c
nfs_nqlease.c
nfs_serv.c
nfs_socket.c
nfs_srvcache.c
nfs_subs.c	The duplicate information returned in fa_type and fa_mode	1995-06-14 06:23:38 +00:00
nfs_syscalls.c
nfs_vfsops.c
nfs_vnops.c
nfs.h
nfsdiskless.h
nfsm_subs.h
nfsmount.h
nfsnode.h
nfsrtt.h
nfsrvcache.h
nfsv2.h
nqnfs.h
rpcv2.h
xdr_subs.h