Fix data race in MemTable::GetBloomFilter() pointer publication #423
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.
Close tikv/tikv#19106
Fix data race in MemTable::GetBloomFilter() on ARM weak memory model introduced in #305 (commit 405de0e)
Use release-acquire memory ordering instead of relaxed to ensure
DynamicBloom object is fully initialized before pointer publication.
Problem:
to be published before DynamicBloom::data_ is initialized
causing crashes
Solution:
only see fully initialized objects
Performance impact:
~1-3 cycles on ARM (may add memory barrier)
filter operations (hash computation + memory access)
The issue was verified using Relacy formal verification tool, which confirmed the data race exists when using relaxed memory ordering.