openbsd/src/lib/libc, branch libressl-v3.0.0

correct mispellings of EACCES; from Kris Katterjohn

2019-07-29T23:14:06+00:00

improve verb-tense for explaining the calling convention of __

2019-07-05T12:55:36+00:00

ok guenther jmc

The last consumer of pre-posix realpath behaviour has stopped

2019-07-05T05:04:26+00:00

requiring it (sftp-server). Remove the /exists///// behaviour from here. The /nonexistant behaviour remains in the kernel and needs to be shot next. There may be ports fallout, but we doubt it. ok beck djm

snprintf/vsnprintf return < 0 on error, rather than -1.

2019-07-03T03:24:04+00:00

tweak previous; ok guenther

2019-06-30T17:31:39+00:00

Document that getcwd() and realpath() are built on system calls that

2019-06-29T21:21:27+00:00

have a different calling convention than the standard function...as seen in kdump output. ok deraadt@ schwarze@

When system calls indicate an error they return -1, not some arbitrary

2019-06-28T13:35:02+00:00

value < 0. errno is only updated in this case. Change all (most?) callers of syscalls to follow this better, and let's see if this strictness helps us in the future.

The C89 standard only requires that atexit(3) returns a non-zero value

2019-06-27T16:30:39+00:00

on error, so checking for -1 only is potentially non-portable. Also mention that the C89 standard does not require errno to be set. OK deraadt@ millert@

sockatmark(3), recv(2), getsockopt(2), and connect(2) return specifically

2019-06-20T14:19:25+00:00

-1 to mark failure, not arbitrary values < 0. I believe manual pages should follow the described contract precisely and accurately.

Remove old realpath(3), and the userland-vs-kernel realpath verification

2019-06-17T03:13:17+00:00

code. We now user the simple userland wrapper on top of __realpath(2). The non-POSIX behaviour still remains, that is the next component to fix. From a diff by beck, but I managed to chainsaw it a bit further. Tested in snaps for a couple of days. ok beck