[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aivBOc_b0YVo2BW1@snips.stderr.spb.ru>
Date: Fri, 12 Jun 2026 11:20:09 +0300
From: Valery Ushakov <uwe@...BSD.org>
To: musl@...ts.openwall.com
Subject: Re: Why do sendmmsg and recvmmsg take unsigned int flags?
On Fri, Jun 12, 2026 at 00:44:35 +0200, Thorsten Glaser wrote:
> On Fri, 12 Jun 2026, Alyssa Ross wrote:
>
> >A little bit more research: it's int on OpenBSD, bionic and uClibc-ng as
> >well, but unsigned int on NetBSD. macOS has a different interface
> >entirely.
>
> Hmm.
>
> TFM says it takes the same flags as sendmsg(2).
>
> Is that unsigned on NetBSD? What does Mac OSX have for sendmsg?
> POSIX has:
> ssize_t sendmsg(int socket, const struct msghdr *message, int flags);
>
> So it probably should be int everywhere (IMHO, not a musl dev).
I'm pretty sure NetBSD's "unsigned" is an unintended incident and is
indeed misaligned with the rest of "int flags" in send/recv. I
forwarded the question:
https://mail-index.netbsd.org/tech-userlevel/2026/06/12/msg014949.html
-uwe
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
