-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only link res_init() on GNU/*nix #47334
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any particular reason why you chose to prefer the original resolver error over any potential
res_init
error?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I considered this but:
That's what the code in
master
is doing. The error fromres_init_if_glibc_before_2_26
is discarded and the original error fromgetaddrinfo()
is returned.Callers are probably expecting
getaddrinfo()
-type errors fromlookup_host()
(e.g.EAI_FAIL
) . This is especially true since this will only be happening on an increasingly small fraction of platforms in obscure cases so it won't get much testing. I think returning theres_init()
result here would be surprising.res_init()
does not return a well defined set of error codes. It's not clear that's it's settingerrno
at all from reading the glibc manageI'm not convinced that
res_init()
will always be the most proximate error. It's possible thatres_init()
is returning a useful report on why the resolution system isn't working (but I have my doubts due to point 3). However, it's also possible that thegetaddrinfo()
is returning more useful information and theres_init()
is failing for some inconsequential reason.I kept the error code return from
on_resolver_failure
in case some platform wants to modify the error on return but it's just directly returned at the moment.If there's a strong opinion in the other direction I can change the error behaviour but I want to reiterate that would be a functional change from
master
.