J. Bruce Fields 1a747ee0cc locks: don't call ->copy_lock methods on return of conflicting locks ... The file_lock structure is used both as a heavy-weight representation of an active lock, with pointers to reference-counted structures, etc., and as a simple container for parameters that describe a file lock. The conflicting lock returned from __posix_lock_file is an example of the latter; so don't call the filesystem or lock manager callbacks when copying to it. This also saves the need for an unnecessary locks_init_lock in the nfsv4 server. Thanks to Trond for pointing out the error. Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu> Cc: Trond Myklebust <Trond.Myklebust@netapp.com>		2008-04-25 13:00:11 -04:00
..
clntlock.c
clntproc.c
host.c	Merge git://git.linux-nfs.org/projects/trondmy/nfs-2.6	2008-04-24 11:46:16 -07:00
Makefile
mon.c
svc4proc.c
svc.c	Merge git://git.linux-nfs.org/projects/trondmy/nfs-2.6	2008-04-24 11:46:16 -07:00
svclock.c	locks: don't call ->copy_lock methods on return of conflicting locks	2008-04-25 13:00:11 -04:00
svcproc.c
svcshare.c
svcsubs.c	lockd: unlock lockd locks held for a certain filesystem	2008-04-25 13:00:11 -04:00
xdr4.c
xdr.c