Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Jan 2021 04:28:56 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 252551] POSIX compliance: writev does not return EINVAL when iovcnt == 0
Message-ID:  <bug-252551-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252551

            Bug ID: 252551
           Summary: POSIX compliance: writev does not return EINVAL when
                    iovcnt =3D=3D 0
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: asomers@FreeBSD.org

POSIX requires that readv and writev return EINVAL when iovcnt =3D=3D 0.  O=
ur 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 =3D=3D 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.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252551-227>