You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

NeilBrown 4a3ae42dc3 [PATCH] knfsd: Correctly handle error condition from lockd_up ... If lockd_up fails - what should we expect? Do we have to later call lockd_down? Well the nfs client thinks "no", the nfs server thinks "yes". lockd thinks "yes". The only answer that really makes sense is "no" !! So: Make lockd_up only increment nlmsvc_users on success. Make nfsd handle errors from lockd_up properly. Make sure lockd_up(0) never fails when lockd is running so that the 'reclaimer' call to lockd_up doesn't need to be error checked. Cc: "J. Bruce Fields" <bfields@fieldses.org> Signed-off-by: Neil Brown <neilb@suse.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>		19 years ago
..
Makefile	…
clntlock.c	[PATCH] knfsd: Correctly handle error condition from lockd_up	19 years ago
clntproc.c	[PATCH] fs: Removing useless casts	19 years ago
host.c	[PATCH] fs: Conversions from kmalloc+memset to k(z|c)alloc	19 years ago
mon.c	LOCKD: Convert to use new rpc_create() API	19 years ago
svc.c	[PATCH] knfsd: Correctly handle error condition from lockd_up	19 years ago
svc4proc.c	…
svclock.c	NLM/lockd: remove b_done	19 years ago
svcproc.c	…
svcshare.c	…
svcsubs.c	[PATCH] fs: Conversions from kmalloc+memset to k(z|c)alloc	19 years ago
xdr.c	…
xdr4.c	…