Jeff Layton e9ba81ee1c lockd: detect and reject lock arguments that overflow ... commit 6930bcbfb6 upstream. lockd doesn't currently vet the start and length in nlm4 requests like it should, and can end up generating lock requests with arguments that overflow when passed to the filesystem. The NLM4 protocol uses unsigned 64-bit arguments for both start and length, whereas struct file_lock tracks the start and end as loff_t values. By the time we get around to calling nlm4svc_retrieve_args, we've lost the information that would allow us to determine if there was an overflow. Start tracking the actual start and len for NLM4 requests in the nlm_lock. In nlm4svc_retrieve_args, vet these values to ensure they won't cause an overflow, and return NLM4_FBIG if they do. Link: https://bugzilla.linux-nfs.org/show_bug.cgi?id=392 Reported-by: Jan Kasiak <j.kasiak@gmail.com> Signed-off-by: Jeff Layton <jlayton@kernel.org> Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Cc: <stable@vger.kernel.org> # 5.14+ Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2022-08-17 14:22:47 +02:00
..
Makefile	…
clnt4xdr.c	…
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	…
svcxdr.h	…
xdr.c	…
xdr4.c	lockd: detect and reject lock arguments that overflow	2022-08-17 14:22:47 +02:00