-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
Change size_t to socklen_t in resolve_address #14464
Conversation
|
|
|
|
|
|
|
1 similar comment
|
|
1 similar comment
|
|
|
|
2 similar comments
|
|
|
|
|
Has the reporter of #13458 confirmed that this branch works? Also, do we have any measure in place to prevent the reoccurrence of this problem in the future? |
@vjpai The reporter referenced to #11390 which has gone stale as a solution that worked for big endian systems. This pull request just adds on changes to make sure that the changes also work for other platforms. As for a measure in place to prevent the recurrence of problem, I think once we remove the usage of reinterpret_cast in our code (or only use it when absolutely necessary), we won't see this anymore. |
Ah, so little endian-ness masks the size difference issue in some cases since socklen_t typically has small values. |
Talked to Nico offline. We don't have the capability to add big endian systems to our test infrastructure currently. Kokoro doesn't support it. |
|
|
|
|
|
|
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.
Please file an issue to find a test platform for this, even if acquiring such a platform is not in the immediate plans.
@dgquintas @markdroth @a11r Need an approval from a code owner :) |
|
|
|
Solves the issue mentioned in #13458
On big endian systems with different sizes for size_t and socklen_t, we will end up with a wrong address length currently.