-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[release/7.0] Fix filtered exceptions when checking for ip forwarding #81157
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue DetailsBackport of #76383 to release/7.0 /cc @rzikm Customer ImpactTestingRiskIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
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
Test failure seems unrelated. (Microsoft.VisualBasic.Core.Tests) |
@ElanHasson Would you be able to test the fix in your repro? The process is:
|
@ElanHasson any chance to try if it really fixes the problem in your specific environment? |
Approved by Tactics for 7.0.4. @karelz @rzikm @wfurt would you like us to wait for @ElanHasson 's confirmation before I merge this? |
I think it is OK to merge @carlossanlop . The fix is pretty small so let's assume it will work as expected. It is best interest of @ElanHasson to still do the validation and let us know if it does not for some reason. |
@ElanHasson it would be really, really useful for next servicing release if you could check it works in next ~24 hours. Do you think it is possible? |
Argh! Accidental misclick on Close PR, sorry! ;( |
@karelz Yep! It's deploying shortly |
@karelz @rzikm @wfurt @wfurt @carlossanlop Thanks! This works on my end in same gVisor environment that had the issue when I reported. Thank you! |
9b70d1f
to
dc23afb
Compare
Closes #81061, #75883.
Backport of #76383 to release/7.0
/cc @rzikm
Customer Impact
Regression in 7.0 from 6.0 breaks customers who need to query IP forwarding details on some constrained systems where IP forwarding information is not available (the appropriate file
/proc/sys/net/ipv(4|6)/conf/{interface}/forwarding
does not exist).A specific example would be Orleans users running in gVisor - see #81061 for more details.
It will also help WSL1 (which is not officially supported) - see #75883.
Testing
Manual testing in WSL1 environment. The affected method no longer throws the exception.
Risk
Low. The change is small and there have been no related problems observed in main (8.0) after merging PR #76383 on 2022/9/30.