Uh oh!
There was an error while loading. Please reload this page.
Don't set security descriptor if the mutex is not owned/new - #120075
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR fixes a mutex access control issue by only setting security permissions when the mutex is newly created. The change prevents unnecessary access control modifications on existing mutexes.
- Only sets mutex access control when
createdNewis true - Adds conditional check around the existing security configuration code
- Maintains the same security model but applies it more selectively
Tagging subscribers to this area: @dotnet/area-system-diagnostics-performancecounter |
Uh oh!
There was an error while loading. Please reload this page.
ericstj
left a comment
There was a problem hiding this comment.
As discussed - you've done manual testing involving multiple users to ensure this is fixed. I imagine we cannot cover this easily in CI.
Uh oh!
There was an error while loading. Please reload this page.
ericstj
commented
Sep 25, 2025
/backport to release/10.0 |
Started backporting to release/10.0: https://github.com/dotnet/runtime/actions/runs/18021213909 |
Fixes#116014.
Fixes#110454.