Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878q8k9m8u.fsf@alyssa.is>
Date: Fri, 12 Jun 2026 10:49:37 +0200
From: Alyssa Ross <hi@...ssa.is>
To: Thorsten Glaser <tg@...bsd.de>, musl@...ts.openwall.com
Subject: Re: Why do sendmmsg and recvmmsg take unsigned int flags?

Thorsten Glaser <tg@...bsd.de> writes:

> 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);

From what I can tell from online man pages, NetBSD and macOS use the standard
prototype for sendmsg.

One further peculiarity is that FreeBSD's and uClibc-ng's sendmmsg
implementations return ssize_t, while every other implementation returns int.

Download attachment "signature.asc" of type "application/pgp-signature" (228 bytes)

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.