trie: make stacktrie not mutate input values#22673
Merged
holiman merged 2 commits intoethereum:masterfrom Apr 16, 2021
Merged
Conversation
gballet
approved these changes
Apr 16, 2021
Member
gballet
left a comment
There was a problem hiding this comment.
LGTM. A bit sad about the stiff increase in allocation numbers, but this way the API is safer.
atif-konasl
pushed a commit
to frozeman/pandora-execution-engine
that referenced
this pull request
Oct 15, 2021
The stacktrie is a bit un-untuitive, API-wise: since it mutates input values. Such behaviour is dangerous, and easy to get wrong if the calling code 'forgets' this quirk. The behaviour is fixed by this PR, so that the input values are not modified by the stacktrie. Note: just as with the Trie, the stacktrie still references the live input objects, so it's still _not_ safe to mutate the values form the callsite.
9 tasks
9 tasks
This was referenced Sep 23, 2022
gzliudan
pushed a commit
to gzliudan/XDPoSChain
that referenced
this pull request
Apr 1, 2025
The stacktrie is a bit un-untuitive, API-wise: since it mutates input values. Such behaviour is dangerous, and easy to get wrong if the calling code 'forgets' this quirk. The behaviour is fixed by this PR, so that the input values are not modified by the stacktrie. Note: just as with the Trie, the stacktrie still references the live input objects, so it's still _not_ safe to mutate the values form the callsite.
19 tasks
gzliudan
pushed a commit
to XinFinOrg/XDPoSChain
that referenced
this pull request
Apr 7, 2025
The stacktrie is a bit un-untuitive, API-wise: since it mutates input values. Such behaviour is dangerous, and easy to get wrong if the calling code 'forgets' this quirk. The behaviour is fixed by this PR, so that the input values are not modified by the stacktrie. Note: just as with the Trie, the stacktrie still references the live input objects, so it's still _not_ safe to mutate the values form the callsite.
gzliudan
pushed a commit
to XinFinOrg/XDPoSChain
that referenced
this pull request
Apr 11, 2025
The stacktrie is a bit un-untuitive, API-wise: since it mutates input values. Such behaviour is dangerous, and easy to get wrong if the calling code 'forgets' this quirk. The behaviour is fixed by this PR, so that the input values are not modified by the stacktrie. Note: just as with the Trie, the stacktrie still references the live input objects, so it's still _not_ safe to mutate the values form the callsite.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The stacktrie is a bit un-untuitive, API-wise: it mutates input values.
This is dangerous, and easy to get wrong if the calling code 'forgets' this quirk, so this PR fixes that behaviour. The first commit provides a testcase, and the second commit provides a fix. Naturally, the fix has an overhead.
With this PR:
Alternative fix:
With alternative fix:
With this PR in, though, we can make some other improvements to not always copy data on input. However, it should be noted that the stacktrie still needs the caller to not mutate the data from the outside, so we cannot remove e.g. example https://github.com/ethereum/go-ethereum/blob/master/core/types/hashing.go#L80:L83 (btw -- the ordinary trie behaves the same way, you're not allowed to mutate input values from the callsite)