[issue29342] os.posix_fadvise misreports errors

Change by Benjamin Peterson : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> os.posix_fallocate() generate exception with errno 0 ___ Python tracker __

[issue29342] os.posix_fadvise misreports errors

Zackery Spytz added the comment: This was fixed in #31106. -- nosy: +ZackerySpytz ___ Python tracker ___ ___ Python-bugs-list maili

[issue29342] os.posix_fadvise misreports errors

Marian Beermann added the comment: Indeed, os.posix_fadvise tries to fetch the error from errno, via posix_error() static PyObject * os_posix_fadvise_impl(PyObject *module, int fd, Py_off_t offset, Py_off_t length, int advice) /*[clinic end generated code: output=412ef4aa70

[issue29342] os.posix_fadvise misreports errors

New submission from Marian Beermann: It has been observed that posix_fadvise will not report the original error if the syscall fails. Eg. https://bugs.alpinelinux.org/issues/6592 >>> os.posix_fadvise(-1, 0, 0, os.POSIX_FADV_DONTNEED) Traceback (most recent call last): File "", line 1, in OSE