Page MenuHomeFreeBSD

getentropy: note that it is nearly POSIX 2024
ClosedPublic

Authored by emaste on Nov 15 2024, 2:46 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Jan 6, 1:19 AM
Unknown Object (File)
Sun, Jan 5, 9:16 AM
Unknown Object (File)
Sun, Jan 5, 7:58 AM
Unknown Object (File)
Sat, Jan 4, 2:57 AM
Unknown Object (File)
Wed, Jan 1, 3:58 AM
Unknown Object (File)
Tue, Dec 31, 3:59 AM
Unknown Object (File)
Mon, Dec 30, 10:13 AM
Unknown Object (File)
Mon, Dec 30, 4:52 AM
Subscribers

Details

Summary
Our implementation diverges from POSIX 2024 in a couple of ways, as
noted in BUGS.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

emaste created this revision.
lib/libc/gen/getentropy.3
86

Does this need a PR?

87

Can you articulate which ones briefly?

lib/libc/gen/getentropy.3
86

OK, PR282783

87

At least EIO instead of EINVAL when len exceeds GETENTROPY_MAX but I haven't checked all values that we return and all that are in 2024.

ziaee added inline comments.
lib/libc/gen/getentropy.3
72–73

In vi(1) we say "is close to".

lib/libc/gen/getentropy.3
18

typo, mention that it nearly conforms to posix 24

lib/libc/gen/getentropy.3
87
This revision is now accepted and ready to land.Nov 20 2024, 7:24 PM