J. Bruce Fields 241f760448 lockd: lockd server-side shouldn't set fl_ops ... BugLink: https://bugs.launchpad.net/bugs/1946802 [ Upstream commit 7de875b231 ] 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> Signed-off-by: Kamal Mostafa <kamal@canonical.com> Signed-off-by: Kelsey Skunberg <kelsey.skunberg@canonical.com>		2021-10-12 16:31:36 -06:00
..
Makefile	…
clnt4xdr.c	…
clntlock.c	…
clntproc.c	…
clntxdr.c	…
host.c	…
mon.c	…
netns.h	…
procfs.c	…
procfs.h	…
svc.c	…
svc4proc.c	…
svclock.c	lockd: lockd server-side shouldn't set fl_ops	2021-10-12 16:31:36 -06:00
svcproc.c	…
svcshare.c	…
svcsubs.c	…
xdr.c	…
xdr4.c	…