J. Bruce Fields 9ce6e29375 lockd: lockd server-side shouldn't set fl_ops ... [ Upstream commit 7de875b231edb807387a81cde288aa9e1015ef9e ] Locks have two sets of op arrays, fl_lmops for the lock manager (lockd or nfsd), fl_ops for the filesystem. The server-side lockd code has been setting its own fl_ops, which leads to confusion (and crashes) in the reexport case, where the filesystem expects to be the only one setting fl_ops. And there's no reason for it that I can see-the lm_get/put_owner ops do the same job. Reported-by: Daire Byrne <daire@dneg.com> Tested-by: Daire Byrne <daire@dneg.com> Signed-off-by: J. Bruce Fields <bfields@redhat.com> Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Sasha Levin <sashal@kernel.org>		2021-09-18 13:40:30 +02:00
..
clnt4xdr.c
clntlock.c
clntproc.c
clntxdr.c
host.c	lockd: don't use interval-based rebinding over TCP	2020-12-30 11:53:30 +01:00
Makefile
mon.c	Replace HTTP links with HTTPS ones: NFS, SUNRPC, and LOCKD clients	2020-09-21 10:21:10 -04:00
netns.h
procfs.c
procfs.h
svc.c
svc4proc.c	lockd: Replace PROC() macro with open code	2020-10-02 09:37:41 -04:00
svclock.c	lockd: lockd server-side shouldn't set fl_ops	2021-09-18 13:40:30 +02:00
svcproc.c	lockd: Replace PROC() macro with open code	2020-10-02 09:37:41 -04:00
svcshare.c
svcsubs.c
xdr.c
xdr4.c