-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Big-endian fixes: networking stack #48398
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue Details
|
src/libraries/System.Private.CoreLib/src/System/Random.Xoshiro256StarStarImpl.cs
Outdated
Show resolved
Hide resolved
Updated Marvin and Xoshiro hashes as discussed above. |
...Net.NetworkInformation/src/System/Net/NetworkInformation/StringParsingHelpers.Connections.cs
Show resolved
Hide resolved
* Fix various places that assumed host byte order was little-endian, use appropriate host <-> network byte order conversion instead. * This in particular affects handling of IPv4 addresses, which are stored internally in network order. * Fix endian assumptions in socket option code (GetSockOpt). * Update test cases and provide /proc test files from a big-endian system.
Fixed merge conflict due to mainline changes (Marvin hash). |
@uweigand I think it'd be helpful to extract the Marvin and System.Text.Json changes into separate PRs so this one can focus on just the networking fixes :) |
Will do, thanks! |
Moved the hash algorithm parts to separate PRs: Only the network part remains in this PR. |
@scalablecory would you mind taking another look? :) |
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.
lgtm
/azp list |
/azp run runtime-libraries-coreclr outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
The failures do not look related to the changes to me:
edit: I'm trying to bump the Helix workitem timeout in #49876 |
Thanks for the PR! |
Fix various places that assumed host byte order was little-endian,
use appropriate host <-> network byte order conversion instead.
This in particular affects handling of IPv4 addresses, which
are stored internally in network order.
Fix endian assumptions in socket option code (GetSockOpt).
Update test cases and provide /proc test files from a
big-endian system.