This repository has been archived by the owner on Jan 22, 2025. It is now read-only.
runtime: fix possible deadlock in in_mem_accounts_index #26046
Merged
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
There is a possible deadlock in in_mem_accounts_index.
self.map()
returns&RwLock<...>
.The first Read lock in fn
items
:solana/runtime/src/in_mem_accounts_index.rs
Lines 143 to 150 in a5f290a
solana/runtime/src/in_mem_accounts_index.rs
Lines 844 to 854 in a5f290a
The second Write lock in fn
put_range_in_cache
:solana/runtime/src/in_mem_accounts_index.rs
Lines 861 to 871 in a5f290a
Summary of Changes
Add
drop(map)
before calling fnhold_range_in_memory
Fixes #