diff options
| author | Miklos Szeredi <mszeredi@redhat.com> | 2025-08-05 18:10:56 +0300 |
|---|---|---|
| committer | Miklos Szeredi <mszeredi@redhat.com> | 2025-08-27 15:29:43 +0300 |
| commit | 7a37f55af7af868119b4fb69285f5fa03ba8cf35 (patch) | |
| tree | fb1ff3541b55e8242111dd751eb24616d3c114a7 /scripts/lib/kdoc/kdoc_output.py | |
| parent | 9d81ba6d49a7457784f0b6a71046818b86ec7e44 (diff) | |
| download | linux-7a37f55af7af868119b4fb69285f5fa03ba8cf35.tar.xz | |
fuse: add COPY_FILE_RANGE_64 that allows large copies
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 and there's no reason why copies
should be limited to 32-bit.
Introduce a new op COPY_FILE_RANGE_64, which is identical, except the
number of bytes copied is returned in a 64-bit value.
If the fuse server does not support COPY_FILE_RANGE_64, fall back to
COPY_FILE_RANGE.
Reported-by: Florian Weimer <fweimer@redhat.com>
Closes: https://lore.kernel.org/all/lhuh5ynl8z5.fsf@oldenburg.str.redhat.com/
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_output.py')
0 files changed, 0 insertions, 0 deletions