kernel_samsung_a53x/include/linux/lockd
Jeff Layton b3c26d143d lockd: set file_lock start and end when decoding nlm4 testargs
[ Upstream commit 7ff84910c66c9144cc0de9d9deed9fb84c03aff0 ]

Commit 6930bcbfb6ce 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: 6930bcbfb6ce ("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: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2024-11-19 12:28:31 +01:00
..
bind.h Keep read and write fds with each nlm_file 2024-11-19 12:27:44 +01:00
debug.h Import A536BXXU9EXDC 2024-06-15 16:02:09 -03:00
lockd.h NLM: Defend against file_lock changes after vfs_test_lock() 2024-11-19 12:27:59 +01:00
nlm.h Import A536BXXU9EXDC 2024-06-15 16:02:09 -03:00
share.h Import A536BXXU9EXDC 2024-06-15 16:02:09 -03:00
xdr.h lockd: detect and reject lock arguments that overflow 2024-11-19 12:28:20 +01:00
xdr4.h lockd: set file_lock start and end when decoding nlm4 testargs 2024-11-19 12:28:31 +01:00