With footnote 28 as follows: "The intent of this list is to specify those circumstances in which an object may or may not be aliased."
Then let's analyze what's wrong here in musl, if anything, and fix it if so. That should shed light on whether there's an issue.
-
-
musl's getaddrinfo looks clean/correct here: https://git.musl-libc.org/cgit/musl/tree/src/network/getaddrinfo.c?h=v1.1.15#n64 …
-
musl's getnameinfo probably has one minor sockaddr aliasing error: https://git.musl-libc.org/cgit/musl/tree/src/network/getnameinfo.c?h=v1.1.15#n131 …
-
res_msend may have a tiny issue if bind() were 3rd-party, but since it's ours and just a syscall, it's ok: https://git.musl-libc.org/cgit/musl/tree/src/network/res_msend.c?h=v1.1.15#n71 …
-
And finally getifaddrs may have some sockaddr aliasing issues; I'm not familiar enough with that code to judge immediately.
-
Everything else in musl looks clean with respect to struct sockaddr.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.