summaryrefslogtreecommitdiff
path: root/fs/lockd/svc4proc.c
diff options
context:
space:
mode:
authorJ. Bruce Fields <bfields@redhat.com>2021-08-21 00:01:59 +0300
committerChuck Lever <chuck.lever@oracle.com>2021-08-21 18:48:34 +0300
commit7de875b231edb807387a81cde288aa9e1015ef9e (patch)
tree02169570bb90ee052d40396055746bd5dca67cba /fs/lockd/svc4proc.c
parent400edd8c0455b9de91d079a4141ff20ba2d221f2 (diff)
downloadlinux-7de875b231edb807387a81cde288aa9e1015ef9e.tar.xz
lockd: lockd server-side shouldn't set fl_ops
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>
Diffstat (limited to 'fs/lockd/svc4proc.c')
0 files changed, 0 insertions, 0 deletions