android_kernel_xiaomi_sm8350/fs/lockd
J. Bruce Fields 727c973ffe 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-22 12:26:34 +02:00
..
clnt4xdr.c
clntlock.c
clntproc.c
clntxdr.c
host.c
Makefile
mon.c
netns.h
procfs.c
procfs.h
svc4proc.c
svc.c
svclock.c lockd: lockd server-side shouldn't set fl_ops 2021-09-22 12:26:34 +02:00
svcproc.c
svcshare.c
svcsubs.c
xdr4.c
xdr.c