[issue26826] Expose new copy_file_range() syscall in os module.

[Giampaolo Rodola']

Giampaolo Rodola' <g.rodola at gmail.com> added the comment:

Little update about this. According to:
http://man7.org/linux/man-pages/man2/copy_file_range.2.html
...it seems glibc 2.27 released on 2018-02-01 includes copy_file_range(). I'm not the best candidate for giving advice on C syscalls definitions/availability, but FWIW this works on my Linux 4.15:

#if defined(__linux__) && \
    defined(SYS_copy_file_range) && \
    defined(__GLIBC_PREREQ) && \
    __GLIBC_PREREQ(2, 27)
...
#endif

I think (but not sure) this is supposed to fix this condition, which appears to be the major blocker here:
https://github.com/python/cpython/blob/9a177061cd7190eabf40efd31e8981e0bccd5dc4/Lib/test/test_os.py#L258-L261

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26826>
_______________________________________