This repository has been archived by the owner on Apr 12, 2021. It is now read-only.
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.
Add nonReentrant to
relayMessage()
#172Add nonReentrant to
relayMessage()
#172Changes from 2 commits
5886e76
2041cbc
25925e2
a3e3f56
52af9e1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW, this code path speaks directly to the rollup contracts (
OVM_CanonicalTransactionChain.enqueue
specifically) so it should not be re-enterable based on the behavior of that target, so it should not be needed.I'd recommend removing it, because the L1
SSTORE
is gonna be expensive. If you think that it's worth keeping, we can, but we should also add it tosendMessage
, since the functions serve similar purposes.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OVM_BaseCrossDomainMessenger.sendMessage()
already has thenonReentrant
modifier on it. You can see above that I moved it down a couple lines to improve the style. But looking at bothsendMessage
andreplayMessage
more closely, I agree that it looks pretty safe to remove them.