triedb/pathdb: fix journal resolution in pathdb #32097
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.
This pull request fixes a flaw in the PBSS state iterator, which could return empty
account or storage data.
In PBSS, multiple in-memory diff layers and a write buffer are maintained. These
layers are persisted to the database and reloaded after node restarts. However,
since the state data is encoded using RLP, the distinction between nil and an empty
byte slice is lost during the encode/decode process. As a result, invalid state values
such as
[]byte{}
can appear in PBSS and ultimately be returned by the state iterator.Checkout https://github.com/ethereum/go-ethereum/blob/master/triedb/pathdb/iterator_fast.go#L270
for more iterator details.
It's a long-term existent issue and now be activated since the snapshot integration.
The error
err="range contains deletion"
will occur when Geth tries to serve otherpeers with SNAP protocol request.