musl/arch/x86_64/bits/socket.h

struct msghdr
{
	void *msg_name;
	socklen_t msg_namelen;
	struct iovec *msg_iov;
	int msg_iovlen, __pad1;
	void *msg_control;
	socklen_t msg_controllen, __pad2;
	int msg_flags;
};
Port musl to x86-64. One giant commit! 2011-02-15 12:32:09 +00:00			`struct msghdr`
			`{`
			`void *msg_name;`
			`socklen_t msg_namelen;`
			`struct iovec *msg_iov;`
workaround broken msghdr struct on 64bit linux POSIX clearly specifies the type of msg_iovlen and msg_controllen, and Linux ignores it and makes them both size_t instead. to work around this we add padding (instead of just using the wrong types like glibc does), but we also need to patch-up the struct before passing it to the kernel in case the caller did not zero-fill it. if i could trust the kernel to just ignore the upper 32 bits, this would not be necessary, but i don't think it will ignore them... 2011-04-08 13:24:19 +00:00			`int msg_iovlen, __pad1;`
Port musl to x86-64. One giant commit! 2011-02-15 12:32:09 +00:00			`void *msg_control;`
workaround broken msghdr struct on 64bit linux POSIX clearly specifies the type of msg_iovlen and msg_controllen, and Linux ignores it and makes them both size_t instead. to work around this we add padding (instead of just using the wrong types like glibc does), but we also need to patch-up the struct before passing it to the kernel in case the caller did not zero-fill it. if i could trust the kernel to just ignore the upper 32 bits, this would not be necessary, but i don't think it will ignore them... 2011-04-08 13:24:19 +00:00			`socklen_t msg_controllen, __pad2;`
Port musl to x86-64. One giant commit! 2011-02-15 12:32:09 +00:00			`int msg_flags;`
			`};`