Date: Mon, 02 Oct 2023 23:23:43 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 206544] sendmsg(2) (sendto(2) too?) can fail with EINVAL; isn't documented in manpage Message-ID: <bug-206544-9-rWQVDIMqCi@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206544-9@https.bugs.freebsd.org/bugzilla/> References: <bug-206544-9@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206544 Peter Jeremy <peterj@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peterj@FreeBSD.org --- Comment #7 from Peter Jeremy <peterj@FreeBSD.org> --- I've bumped into the lack of documentation as well, though the triggers were hidden far more deeply in the kernel: 1) An incorrect cmsg_len will typically trigger EINVAL. 2) Using IPv6-level messages (i.e. cmsg_level=3D=3DIPPROTO_IPV6) with at IPv4-mapped IPv6 connection will trigger EINVAL in at least some cases. This appears to be a duplicate of bug 99356. I won't close it as a duplica= te because there's different analysis in both bugs. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206544-9-rWQVDIMqCi>