J. Bruce Fields 5996a298da NLM: don't unlock on cancel requests ... Currently when lockd gets an NLM_CANCEL request, it also does an unlock for the same range. This is incorrect. The Open Group documentation says that "This procedure cancels an *outstanding* blocked lock request." (Emphasis mine.) Also, consider a client that holds a lock on the first byte of a file, and requests a lock on the entire file. If the client cancels that request (perhaps because the requesting process is signalled), the server shouldn't apply perform an unlock on the entire file, since that will also remove the previous lock that the client was already granted. Or consider a lock request that actually *downgraded* an exclusive lock to a shared lock. Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>		2006-01-06 14:58:53 -05:00
..
clntlock.c
clntproc.c	RPC: Clean up RPC task structure	2006-01-06 14:58:39 -05:00
host.c
Makefile
mon.c
svc.c	SUNRPC: Ensure that SIGKILL will always terminate a synchronous RPC call.	2006-01-06 14:58:45 -05:00
svc4proc.c	RPC: Clean up RPC task structure	2006-01-06 14:58:39 -05:00
svclock.c	NLM: don't unlock on cancel requests	2006-01-06 14:58:53 -05:00
svcproc.c	RPC: Clean up RPC task structure	2006-01-06 14:58:39 -05:00
svcshare.c
svcsubs.c
xdr.c
xdr4.c