Ian Dowse 4f6434bdde Now that nfsm_reply() does not usually set 'error' to 0, we need ... to do it explicitly in nfsrv_noop so that the reply gets sent back to the client. This fixes the generation of a selection of RPC error replies (RPC_PROGMISMATCH, RPC_PROGUNAVAIL, RPC_PROCUNAVAIL etc.) that are used by some clients to detect support for optional protocols and features. Reviewed by: peter Reported by: Thomas Quinot <quinot@inf.enst.fr> PR: kern/31479		2001-10-25 19:07:56 +00:00
..
nfs_serv.c	Now that nfsm_reply() does not usually set 'error' to 0, we need	2001-10-25 19:07:56 +00:00
nfs_srvcache.c	Unwind some more macros. NFSMADV() was kinda silly since it was right	2001-09-28 04:37:08 +00:00
nfs_srvsock.c	Unwind some more macros. NFSMADV() was kinda silly since it was right	2001-09-28 04:37:08 +00:00
nfs_srvsubs.c	Unwind some more macros. NFSMADV() was kinda silly since it was right	2001-09-28 04:37:08 +00:00
nfs_syscalls.c	Unwind some more macros. NFSMADV() was kinda silly since it was right	2001-09-28 04:37:08 +00:00
nfs.h	Unwind some more macros. NFSMADV() was kinda silly since it was right	2001-09-28 04:37:08 +00:00
nfsm_subs.h	Unwind some more macros. NFSMADV() was kinda silly since it was right	2001-09-28 04:37:08 +00:00
nfsrvcache.h	Cleanup and split of nfs client and server code.	2001-09-18 23:32:09 +00:00
nfsrvstats.h	Cleanup and split of nfs client and server code.	2001-09-18 23:32:09 +00:00