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.

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>		17 years ago
..
Makefile	…
clntlock.c	…
clntproc.c	…
host.c	Merge git://git.linux-nfs.org/projects/trondmy/nfs-2.6	17 years ago
mon.c	…
svc.c	Merge git://git.linux-nfs.org/projects/trondmy/nfs-2.6	17 years ago
svc4proc.c	…
svclock.c	locks: don't call ->copy_lock methods on return of conflicting locks	17 years ago
svcproc.c	…
svcshare.c	lockd: fix sparse warning in svcshare.c	17 years ago
svcsubs.c	lockd: unlock lockd locks held for a certain filesystem	17 years ago
xdr.c	…
xdr4.c	…