This repository was archived by the owner on Jan 22, 2025. It is now read-only.
Fix - Uses fetch_add()
to accumulate usage counters in LoadedPrograms
#34319
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The pattern
load()
,saturating_add_assign()
,store()
on an atomic counter is a race condition because it does not use the transactional properties of atomics. AlsoDelayVisibility
tombstones currently don't have their usage counter incremented on use.Summary of Changes
While
fetch_add()
gives up the saturating arithmetic, this is first of all an extremely improbable edge case as even with the wildest TPS numbers currently envisioned a single validator would still have to run for tens of thousands of years without a single reboot and all transactions only using a single program, for this 64 bit counter to ever overflow. And even if it does, the atomics do wrapping and do not panic, so it is self correcting.