storagefsm: Fix double unlock with ready WaitDeals sectors #5783
Conversation
This file contains 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.
We would double-unlock the
inputLkwhen the miner had a sector in WaitDeals state become ready for sealing while the node wasn't runningSomehow those unlocks got left there when this was refactored, and would cause double unlock with the unlock here -> https://github.com/filecoin-project/lotus/blob/master/extern/storage-sealing/input.go#L33
Looked at other usages of this lock, and it seems like we don't have more cases of this
(manually reproduced and verified the fix on my node)