This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients gregory.p.smith, kevans91
Date 2020-10-11.18:48:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1602442099.98.0.0996774522491.issue40423@roundup.psfhosted.org>
In-reply-to
Content
for reference, very recent Linux kernels appear to have gained a close_range syscall.  http://lkml.iu.edu/hypermail/linux/kernel/2008.0/02649.html

Your diff isn't quite sufficient as is.  When depending on a syscall that has a function provided by libc, the libc function may exist (thus HAVE_CLOSE_RANGE will be true at Python compile time) but the system the process is running on may not support the system call.  So it'll return an EINVAL (or something like that) error.

Special handling of that error to add an `else {...}` falling back to the other codepath is necessary.
History
Date User Action Args
2020-10-11 18:48:20gregory.p.smithsetrecipients: + gregory.p.smith, kevans91
2020-10-11 18:48:19gregory.p.smithsetmessageid: <1602442099.98.0.0996774522491.issue40423@roundup.psfhosted.org>
2020-10-11 18:48:19gregory.p.smithlinkissue40423 messages
2020-10-11 18:48:19gregory.p.smithcreate