Jeff Layton 7ff84910c6 lockd: set file_lock start and end when decoding nlm4 testargs ... 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>		2023-03-14 14:00:55 -04:00
..
bind.h	Keep read and write fds with each nlm_file	2021-08-23 18:05:31 -04:00
debug.h
lockd.h	NFSD 6.3 Release Notes	2023-02-22 14:21:40 -08:00
nlm.h
share.h
xdr.h	filelock: move file locking definitions to separate header file	2023-01-11 06:52:32 -05:00
xdr4.h	lockd: set file_lock start and end when decoding nlm4 testargs	2023-03-14 14:00:55 -04:00