diff options
| author | Florian Weimer <fweimer@redhat.com> | 2025-08-02 12:44:51 +0200 |
|---|---|---|
| committer | Florian Weimer <fweimer@redhat.com> | 2025-08-05 15:25:18 +0200 |
| commit | 9a2aceb076b8aa6ffa8edb4adcc9f43a2d3a352d (patch) | |
| tree | 7360800115fdac5087f6ce01c38268d58995ec64 /sysdeps/unix/mips/mips64 | |
| parent | e5363e6f460c2d58809bf10fc96d70fd1ef8b5b2 (diff) | |
| download | glibc-master.zip glibc-master.tar.gz glibc-master.tar.bz2 | |
The copy_file_range system call seems to be the only one that can
return an off64_t value. Use FUSE to exercise this, without actually
creating such large files or copying any data. Due to FUSE protocol
limitations, only sizes up to UINT_MAX can be tested, but this is
sufficient to check for the presence of bug 33245.
The FUSE protocol limitations are raised here:
copy_file_range return value on FUSE
<https://lore.kernel.org/all/lhuh5ynl8z5.fsf@oldenburg.str.redhat.com/>
Reviewed-by: Sam James <sam@gentoo.org>
Reviewed-by: Collin Funk <collin.funk1@gmail.com>
Diffstat (limited to 'sysdeps/unix/mips/mips64')
0 files changed, 0 insertions, 0 deletions