posix_fallocate(2) && posix_fadvise(2) are somewhat broken

2015-12-08 Thread Maxim Sobolev
Hi, while working on some unrelated feature I've noticed that at least those two system calls are not returning proper value (-1) on error. Instead actual errno value is returned from the syscall verbatim, i.e. posix_fadvise() returns 22 on EINVAL. Attached patch fixes that problem, however I am

Re: posix_fallocate(2) && posix_fadvise(2) are somewhat broken

2015-12-08 Thread Dag-Erling Smørgrav
Maxim Sobolev writes: > Hi, while working on some unrelated feature I've noticed that at least > those two system calls are not returning proper value (-1) on error. > Instead actual errno value is returned from the syscall verbatim, > i.e. posix_fadvise() returns 22 on

Re: posix_fallocate(2) && posix_fadvise(2) are somewhat broken

2015-12-08 Thread Maxim Sobolev
Ah, ok, I see now. It's been broken and still broken in 9.x/10.x, already fixed in trunk and I been just reading wrong manpage. Thanks for the pointer, on a related note those fixes should probably be MFCed into 10.3 if it has not been already. On Tue, Dec 8, 2015 at 9:42 AM, Konstantin Belousov

Re: posix_fallocate(2) && posix_fadvise(2) are somewhat broken

2015-12-08 Thread Garrett Wollman
In article sobo...@freebsd.org writes: >Hi, while working on some unrelated feature I've noticed that at least >those two system calls are not returning proper value (-1) on error. >Instead actual errno value is returned from

Re: posix_fallocate(2) && posix_fadvise(2) are somewhat broken

2015-12-08 Thread Maxim Sobolev
Then it's documentation bug or maybe some discrepancy between SUS and POSIX. $ man posix_fadvise RETURN VALUES The posix_fadvise() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indicate the error. STANDARDS

Re: posix_fallocate(2) && posix_fadvise(2) are somewhat broken

2015-12-08 Thread Mark Johnston
On Tue, Dec 08, 2015 at 01:35:31AM -0800, Maxim Sobolev wrote: > Hi, while working on some unrelated feature I've noticed that at least > those two system calls are not returning proper value (-1) on error. > Instead actual errno value is returned from the syscall verbatim, > i.e. posix_fadvise()

Re: posix_fallocate(2) && posix_fadvise(2) are somewhat broken

2015-12-08 Thread Konstantin Belousov
On Tue, Dec 08, 2015 at 04:52:05PM +0100, Dag-Erling Sm??rgrav wrote: > Maxim Sobolev writes: > > Hi, while working on some unrelated feature I've noticed that at least > > those two system calls are not returning proper value (-1) on error. > > Instead actual errno value is

Re: posix_fallocate(2) && posix_fadvise(2) are somewhat broken

2015-12-08 Thread Dag-Erling Smørgrav
Konstantin Belousov writes: > Dag-Erling Smørgrav writes: > > Maxim Sobolev writes: > > > Hi, while working on some unrelated feature I've noticed that at least > > > those two system calls are not returning proper value (-1) on error. > >

Re: posix_fallocate(2) && posix_fadvise(2) are somewhat broken

2015-12-08 Thread Konstantin Belousov
On Tue, Dec 08, 2015 at 07:54:06PM +0100, Dag-Erling Sm??rgrav wrote: > Konstantin Belousov writes: > > Dag-Erling Sm??rgrav writes: > > > Maxim Sobolev writes: > > > > Hi, while working on some unrelated feature I've noticed that at least