-
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
make sure we process PhysicalAddress on Linux #42878
Conversation
Tagging subscribers to this area: @dotnet/ncl |
Looks like wrong issue? |
updated. correct number wrong repo - this was done back in corefx before the consolidation. |
Can you help me understand what in that change broke this? |
In the past, we would walk the interface list and then for each address type we would invoke appropriate managed callback which would be building the resulting structure. That was inefficient as well as we could not handle certain cases. So with the change we put everything to single array passed from native side and we processes it in two linear passes on managed side. I hope this makes some sense @geoffkizer. Updated test would be sufficient to catch this e.g. test for some specific data. |
Thanks for quick fix @wfurt. Let's get a 5.0 PR up with the template? Are there any other missing test cases you see around this API? |
/backport release/5.0 |
/backport to release/5.0 |
Started backporting to release/5.0: https://github.com/dotnet/runtime/actions/runs/279989116 |
This is regression to 3.1 caused by dotnet/corefx#41490. Somehow the lack of MAC address got unnoticed as GetPhysicalAddress() simple returns empty address instead of failing.
I modified tests to ensure valid length at least for Ethernet type.
Provided repro now shows correct output:
fixes #42870