bindresvport has never been thread-safe before and AFAIK no other system that has the function makes it thread-safe. Like all functions, if it's not specifically documented and being thread-safe, it isn't. I don't see the rationale for requiring bindresvport to be thread-safe now.