Fix PerformanceCounterLib cache races - #132035
Conversation
Capture initialized cache tables before returning so concurrent invalidation cannot turn a successful lookup into null. Synchronize shared library-table enumeration with creation and replacement. Fix dotnet#90803
|
Azure Pipelines: Successfully started running 3 pipeline(s). 13 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
|
@jaideeppyne please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
|
Tagging subscribers to this area: @dotnet/area-system-diagnostics-performancecounter |
Fixes #90803.
Root cause
CloseAllTablescan clear a cache field after its getter has initialized it but before the getter rereads the field for its return value. That turns a successful initialization into a null return. Separately,CloseAllTablesenumeratess_libraryTablewithout the lock used byGetPerformanceCounterLib, so concurrent library creation can mutate theHashtableduring enumeration.Changes
InternalSyncObjectwhile enumerating and clearing the shared library table.No public API or intended cache-invalidation behavior changes. A caller already using a cache may finish using that snapshot while invalidation causes subsequent callers to rebuild it.
Validation
git diff --check— passed../dotnet.sh build src/libraries/System.Diagnostics.PerformanceCounter/src/System.Diagnostics.PerformanceCounter.csproj -f net11.0-windows -c Release --no-restore— passed with 0 warnings and 0 errors.The runtime behavior and test suite are Windows-only, so they cannot execute on the macOS development host; the Windows-target implementation and its analyzers were compiled successfully. CI provides the Windows runtime coverage.
Risk and rollback
Risk is limited to synchronization in the internal performance-counter cache. The additional lock reuses the lock already taken for every
s_libraryTablemutation. Rollback is a single commit revert.AI assistance was used for repository exploration and drafting; I reviewed the patch and validation results and will personally address review feedback.