The structure is initialized, which can cause problems e.g. with
its nl_pid member.
To quote from an LLM report in GL#6257:
> A non-zero nl_pid is an explicit netlink port-ID request, so the
> kernel either binds the socket to an arbitrary port ID (functionally
> tolerable for a multicast-only listener, but it can squat another
> process's natural port ID) or fails with EADDRINUSE when the garbage
> value collides with an existing NETLINK_ROUTE socket in the same
> namespace.
Zero initialize the structure.
route_socket(uv_os_sock_t *fdp) {
uv_os_sock_t fd = -1;
#ifdef USE_NETLINK
- struct sockaddr_nl sa;
+ struct sockaddr_nl sa = { 0 };
int r;
#endif