Miklos Szeredi 532b87643f fuse: prevent overflow in copy_file_range return value ... commit 1e08938c36 upstream. The FUSE protocol uses struct fuse_write_out to convey the return value of copy_file_range, which is restricted to uint32_t. But the COPY_FILE_RANGE interface supports a 64-bit size copies. Currently the number of bytes copied is silently truncated to 32-bit, which may result in poor performance or even failure to copy in case of truncation to zero. Reported-by: Florian Weimer <fweimer@redhat.com> Closes: https://lore.kernel.org/all/lhuh5ynl8z5.fsf@oldenburg.str.redhat.com/ Fixes: 88bc7d5097 ("fuse: add support for copy_file_range()") Cc: <stable@vger.kernel.org> # v4.20 Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2025-09-19 16:35:46 +02:00
..
Kconfig	…
Makefile	…
acl.c	…
control.c	…
cuse.c	…
dax.c	…
dev.c	…
dir.c	fuse: fix race between concurrent setattrs from multiple nodes	2025-07-06 11:01:32 +02:00
file.c	fuse: prevent overflow in copy_file_range return value	2025-09-19 16:35:46 +02:00
fuse_i.h	…
fuse_trace.h	…
inode.c	…
ioctl.c	…
iomode.c	…
passthrough.c	fuse: do not allow mapping a non-regular backing file	2025-09-19 16:35:46 +02:00
readdir.c	…
virtio_fs.c	…
xattr.c	…