lockd: adapt to breakup of struct file_lock
Most of the existing APIs have remained the same, but subsystems that access file_lock fields directly need to reach into struct file_lock_core now. Signed-off-by:Jeff Layton <jlayton@kernel.org> Link: https://lore.kernel.org/r/20240131-flsplit-v3-40-c6129007ee8d@kernel.org Reviewed-by:
NeilBrown <neilb@suse.de> Signed-off-by:
Christian Brauner <brauner@kernel.org>
Showing
- fs/lockd/clnt4xdr.c 7 additions, 7 deletionsfs/lockd/clnt4xdr.c
- fs/lockd/clntlock.c 1 addition, 1 deletionfs/lockd/clntlock.c
- fs/lockd/clntproc.c 33 additions, 29 deletionsfs/lockd/clntproc.c
- fs/lockd/clntxdr.c 7 additions, 7 deletionsfs/lockd/clntxdr.c
- fs/lockd/svc4proc.c 5 additions, 5 deletionsfs/lockd/svc4proc.c
- fs/lockd/svclock.c 33 additions, 31 deletionsfs/lockd/svclock.c
- fs/lockd/svcproc.c 5 additions, 5 deletionsfs/lockd/svcproc.c
- fs/lockd/svcsubs.c 10 additions, 10 deletionsfs/lockd/svcsubs.c
- fs/lockd/xdr.c 7 additions, 7 deletionsfs/lockd/xdr.c
- fs/lockd/xdr4.c 7 additions, 7 deletionsfs/lockd/xdr4.c
- include/linux/lockd/lockd.h 4 additions, 4 deletionsinclude/linux/lockd/lockd.h
- include/linux/lockd/xdr.h 0 additions, 1 deletioninclude/linux/lockd/xdr.h
Please register or sign in to comment