Jeff Layton ed1869a252 lockd: set file_lock start and end when decoding nlm4 testargs ... commit 7ff84910c6 upstream. Commit 6930bcbfb6 dropped the setting of the file_lock range when decoding a nlm_lock off the wire. This causes the client side grant callback to miss matching blocks and reject the lock, only to rerequest it 30s later. Add a helper function to set the file_lock range from the start and end values that the protocol uses, and have the nlm_lock decoder call that to set up the file_lock args properly. Fixes: 6930bcbfb6 ("lockd: detect and reject lock arguments that overflow") Reported-by: Amir Goldstein <amir73il@gmail.com> Signed-off-by: Jeff Layton <jlayton@kernel.org> Tested-by: Amir Goldstein <amir73il@gmail.com> Cc: stable@vger.kernel.org #6.0 Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com> Signed-off-by: Amir Goldstein <amir73il@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2023-03-30 12:47:56 +02:00
..
Makefile	…
clnt4xdr.c	lockd: set file_lock start and end when decoding nlm4 testargs	2023-03-30 12:47:56 +02:00
clntlock.c	…
clntproc.c	…
clntxdr.c	…
host.c	…
mon.c	…
netns.h	…
procfs.c	…
procfs.h	…
svc.c	…
svc4proc.c	lockd: detect and reject lock arguments that overflow	2022-08-17 14:22:47 +02:00
svclock.c	…
svcproc.c	…
svcshare.c	…
svcsubs.c	lockd: set other missing fields when unlocking files	2022-12-31 13:14:05 +01:00
svcxdr.h	…
xdr.c	…
xdr4.c	lockd: set file_lock start and end when decoding nlm4 testargs	2023-03-30 12:47:56 +02:00