-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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/8.0-staging] Support setting ACLs on file paths longer than MAX_PATH
#109674
[release/8.0-staging] Support setting ACLs on file paths longer than MAX_PATH
#109674
Conversation
Co-authored-by: Adam Sitnik <adam.sitnik@gmail.com>
Tagging subscribers to this area: @dotnet/area-system-io |
@adamsitnik @jeffhandley friendly reminder that today's Code Complete day for the February 2025 Release. If you want this PR included in that release ,please make sure it gets a Tactics approval, a sign-off from an area owners, the CI failures are investigated, and merged before 4pm PT. Otherwise it will have to wait until next month. |
@adamsitnik @jeffhandley Today is code complete for the April Release. If you want this fix included in this release, please get it approved by Tactics and merge it before 4pm PT. |
The 'check-labels' check is in a bad state. I'm going to close this PR and replace it with a fresh backport PR. |
Backport of #92460 to release/8.0-staging
/cc @jeffhandley @karakasa @adamsitnik
Customer Impact
Customer @AliveDevil requested this fix be backported to the LTS .NET 8 release, with the following comments:
Regression
Testing
This fix was merged into .NET 9 in September 2023, and has been in place since Preview 1. A new unit test was added as part of the original fix, and the fix also reuses an existing approach and
PathInternal.EnsureExtendedPrefixIfNeeded
helper method.Risk
Low. Targeted fix for the specific ACL scenario.