[Bug 252551] POSIX compliance: writev does not return EINVAL when iovcnt == 0
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Jan 10 04:28:56 UTC 2021
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252551
Bug ID: 252551
Summary: POSIX compliance: writev does not return EINVAL when
iovcnt == 0
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: bugs at FreeBSD.org
Reporter: asomers at FreeBSD.org
POSIX requires that readv and writev return EINVAL when iovcnt == 0. Our own
man pages document that condition as well.
https://pubs.opengroup.org/onlinepubs/9699919799/functions/writev.html
https://pubs.opengroup.org/onlinepubs/9699919799/functions/readv.html
However, we accept iovcnt == 0, do nothing, and return 0. That's not
inherently unreasonable, but it's not POSIX-compliant. From inspection,
OpenBSD and NetBSD do not have this bug, but DragonflyBSD does.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list