This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: posix_fallocate / How to go from a POSIX interpretation # to Austin Group Bug ID?
- From: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- To: Carlos O'Donell <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Wed, 30 Sep 2015 11:16:49 +0100
- Subject: Re: posix_fallocate / How to go from a POSIX interpretation # to Austin Group Bug ID?
- Authentication-results: sourceware.org; auth=none
- References: <560AD5F4 dot 6060805 at redhat dot com>
On 29/09/15 19:18, Carlos O'Donell wrote:
In working on posix_fallocate recently I noticed that for Issue 7
the wording for EINVAL had been changed.
The Issue 7 text says:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/posix_fallocate.html
~~~
Issue 7
Austin Group Interpretations 1003.1-2001 #022, #024, and #162 are applied, changing the definition of the [EINVAL] error.
~~~
Is there any way to go from those interpretation #s to Austin Group Bug
numbers (http://austingroupbugs.net/main_page.php)?
https://collaboration.opengroup.org/austin/interps/documents.php
it's a pain to use..
https://collaboration.opengroup.org/austin/interps/documents/4882/AI-022.txt
https://collaboration.opengroup.org/austin/interps/documents/4885/AI-024.txt
https://collaboration.opengroup.org/austin/interps/documents/14574/AI-162.txt
I'd like to read those issues and the final interpretations.
If I'm right then failure of pread in our emulation should return EINVAL
instead of EBADF (kernel error for failed pread on O_WRONLY file) to indicate
that posix_fallocate can't be supported.
Cheers,
Carlos.