Description of problem:
ssize_t copy_file_range(int fd_in, loff_t *off_in,
int fd_out, loff_t *off_out,
size_t len, unsigned int flags);
ssize_t copy_file_range (int __infd, __off64_t *__pinoff,
int __outfd, __off64_t *__poutoff,
size_t __length, unsigned int __flags);
Note loff_t versus __off64_t
AFAICT loff_t is a kernel type that is not usually used in user space.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
And it's causing confusion for gluster devs who are copying the man page but are puzzled by the discrepancy between the man page and the decl in <unistd.h>
copy_file_range.2 man page describes Linux system call (section 2 - system calls (functions provided by the kernel)), so I believe the use of loff_t is appropriate.
__off64_t seems to be a type private to glibc.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.