readlink: get rid of weird partial-buffer semantics carried over from posix

but follow posix in returning ERANGE when the result is too big
This commit is contained in:
Pat Hickey
2021-01-04 16:41:24 -08:00
parent 84318024ef
commit 222a57868e
5 changed files with 14 additions and 51 deletions

View File

@@ -23,10 +23,6 @@ wasi_tests::path_symlink_trailing_slashes
- unclear, path_symlink is giving a ENOTDIR when it expects an EEXIST...
wasi_tests::poll_oneoff
- no sched yet
wasi_tests::readlink
- insists on small buffer semantics for readlink that don't seem right
wasi_tests::readlink_no_buffer
- insists on small buffer semantics for readlink that don't seem right
wasi_tests::remove_directory_trailing_slashes
- apparently cap-std gives EINVAL when trying to remove dir with
trailing slash?