Andrew Kelley
062d17ccab
std: fix msghdr and cmsghdr when using musl libc
...
glibc and linux kernel use size_t for some field lengths while POSIX and
musl use int. This bug would have caused breakage the first time someone
tried to call sendmsg on a 64-bit big endian system when linking musl
libc.
my opinion:
* msghdr.iovlen: kernel and glibc have it right. This field should
definitely be size_t. With int, the padding bytes are wasted for no
reason.
* msghdr.controllen: POSIX and musl have it right. 4 bytes is plenty for
the length, and it saves 4 bytes next to flags.
* cmsghdr.len: POSIX and musl have it right. 4 bytes is plenty for the
length, and it saves 4 bytes since the other fields are also 32-bits
each.
2025-10-02 16:30:59 -07:00
..
2025-09-30 13:44:51 +01:00
2025-08-25 16:15:17 +02:00
2025-09-30 13:44:54 +01:00
2025-09-30 18:28:47 -07:00
2025-09-20 18:33:00 -07:00
2025-10-02 15:27:35 +02:00
2025-09-30 13:44:51 +01:00
2025-07-07 22:43:51 -07:00
2025-10-02 16:30:59 -07:00
2025-09-18 22:39:33 -07:00
2025-09-30 13:44:54 +01:00
2025-10-02 16:30:59 -07:00
2025-10-02 16:30:59 -07:00
2025-09-21 04:55:39 -07:00
2025-09-18 12:42:24 +02:00
2025-09-03 21:46:01 -07:00
2025-04-13 02:20:32 -04:00
2025-10-02 16:30:59 -07:00
2025-10-02 16:30:59 -07:00
2025-09-22 01:37:32 +02:00
2025-09-24 03:12:28 +02:00
2025-09-18 22:39:33 -07:00
2025-09-17 19:54:15 -07:00
2025-08-29 17:14:26 -07:00
2025-09-18 12:42:24 +02:00
2025-09-30 13:44:54 +01:00
2025-10-02 16:30:59 -07:00
2025-03-08 14:25:28 -05:00
2025-09-18 22:39:33 -07:00
2025-07-11 08:17:43 +02:00
2025-09-26 05:28:46 -07:00
2025-09-20 18:33:00 -07:00
2025-09-30 19:33:03 -07:00
2025-09-20 14:34:18 -07:00
2025-08-31 12:49:18 -07:00
2025-08-25 16:15:17 +02:00
2025-08-28 18:30:57 -07:00
2025-07-01 23:03:15 +02:00
2025-08-11 15:52:49 -07:00
2025-09-30 13:44:51 +01:00
2025-09-30 13:44:51 +01:00
2025-10-02 16:30:59 -07:00
2025-09-30 13:44:49 +01:00
2025-07-31 22:10:11 -07:00
2025-09-17 20:05:23 -07:00
2025-10-01 23:47:47 +02:00
2025-09-20 14:34:18 -07:00
2025-04-03 15:57:35 -07:00
2024-08-22 08:44:08 +02:00
2025-09-30 13:44:53 +01:00
2025-09-30 13:44:53 +01:00
2025-07-31 22:10:22 +01:00
2025-09-19 05:02:22 +00:00
2025-10-02 16:30:59 -07:00
2025-05-21 13:01:21 +03:30
2025-09-11 00:18:37 -07:00
2025-07-31 22:10:11 -07:00
2025-08-20 18:21:32 +02:00
2025-08-17 14:42:57 +02:00
2025-10-02 16:30:59 -07:00
2025-08-29 17:14:26 -07:00
2025-08-29 17:14:26 -07:00
2025-09-18 22:39:33 -07:00
2025-09-30 13:44:51 +01:00
2025-08-30 06:36:41 +02:00
2025-10-02 16:30:59 -07:00
2025-09-20 18:33:00 -07:00
2025-09-20 14:34:18 -07:00
2025-10-02 16:30:59 -07:00
2024-08-27 00:44:35 +01:00
2025-09-19 05:02:22 +00:00
2025-08-29 17:14:26 -07:00
2025-09-22 18:36:47 +02:00
2025-10-02 16:30:59 -07:00
2025-08-11 15:52:49 -07:00
2025-02-01 19:02:39 +01:00
2025-08-29 17:14:26 -07:00
2025-10-02 16:30:59 -07:00
2025-10-02 16:30:59 -07:00
2025-08-29 17:14:26 -07:00
2025-09-19 04:01:08 +02:00
2025-04-03 14:55:04 -07:00
2024-09-23 13:03:06 -07:00
2025-10-02 16:30:59 -07:00
2025-10-02 16:30:59 -07:00
2025-07-22 09:41:44 -07:00
2025-09-20 18:33:00 -07:00
2025-10-02 16:30:59 -07:00
2025-10-02 16:30:59 -07:00
2025-07-12 17:18:53 +00:00
2025-08-11 15:52:49 -07:00
2025-08-28 18:30:57 -07:00
2025-08-31 12:49:18 -07:00
2025-08-31 12:49:18 -07:00
2025-07-16 10:27:39 -07:00
2025-01-15 15:11:36 -08:00
2025-09-24 20:01:18 -07:00
2025-08-29 17:14:26 -07:00
2025-08-15 23:35:16 +02:00